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

[paquin pierre]

Hello,

You spoke about a fixed in your comment on 2021-06-22
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/comments/30
. Is that to say that no fix will be part of Ubuntu next LTS version
22.04?

I see your link on mesa. No reponse since 8 months. In your comment on
2021-03-05 you sid "The fix isn't in the 21.0 branch yet. Only on master
(22)." => is that to say that Ubuntu 22.04 will have the fix ?

Thanks

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

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

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

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

  ---

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

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

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

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

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


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

[Touch-packages] [Bug 1938998] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not
  render properly

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with
  Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5,
  upgrading to a specific mesa and xorg-server version, followed by a
  system restart, led to the Cinnamon desktop not rendering correctly,
  such that the desktop was unusable. The rendering problem is that
  icons and menus are displayed as grey rectangles and it's not possible
  to see what they are.

  I believe the problem is in one of these packages:

  * mesa 21.0.3-0ubuntu0.2-20.04.1
  * xorg-server 2:1.20.11-1ubuntu1-20.04.2

  Restoring the system from backup, and then upgrading but omitting the above 
two updates and restarting, the system behaves as expected. It's not 
immediately clear which of these packages is causing the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinay  1218 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (187 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
   
   tailscale0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic 
root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-80-generic N/A
   linux-backports-modules-5.4.0-80-generic  N/A
   linux-firmware1.187.15
  RfKill:
   
  Tags:  ulyssa
  Uname: Linux 5.4.0-80-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly

[Daniel van Vugt]

Is this bug still happening? If so then with what package versions?


** Tags added: focal

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

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

Title:
  [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not
  render properly

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with
  Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5,
  upgrading to a specific mesa and xorg-server version, followed by a
  system restart, led to the Cinnamon desktop not rendering correctly,
  such that the desktop was unusable. The rendering problem is that
  icons and menus are displayed as grey rectangles and it's not possible
  to see what they are.

  I believe the problem is in one of these packages:

  * mesa 21.0.3-0ubuntu0.2-20.04.1
  * xorg-server 2:1.20.11-1ubuntu1-20.04.2

  Restoring the system from backup, and then upgrading but omitting the above 
two updates and restarting, the system behaves as expected. It's not 
immediately clear which of these packages is causing the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinay  1218 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-01-30 (187 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
   
   tailscale0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic 
root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-80-generic N/A
   linux-backports-modules-5.4.0-80-generic  N/A
   linux-firmware1.187.15
  RfKill:
   
  Tags:  ulyssa
  Uname: Linux 5.4.0-80-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1632529] Re: sound problem

[Launchpad Bug Tracker]

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  sound problem

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I am experiencing this problem everytime even though I reinstalled the
  entire linux system. The same audio problem exists everytime.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rajeev 1716 F pulseaudio
  Date: Tue Oct 11 20:26:11 2016
  InstallationDate: Installed on 2016-10-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to xenial on 2016-10-12 (0 days ago)
  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:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1632529/+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 1951879] Re: System freezes after right clicking on a dock icon

[Daniel van Vugt]

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

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.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

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.


** Summary changed:

- System freezes
+ System freezes after right clicking on a dock icon

** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(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/1951879

Title:
  System freezes after right clicking on a dock icon

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  The problem can be reproduced as follow in ubuntu 21.10:
  - run jedit (which was insalled with sudo apt install jedit)
  - jedit starts and is working fine, but a right click on its icon in the dock 
freezes the system
  - it is still possible to log into the system using ssh and I noticed that 
gnome-shell is using 100% of a CPU.
  - the system does not recover without shutting it down and restarting it
  - the problem could be reproduced on a lenovo laptop as well as in a VM

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 22 21:24:51 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2021-11-22 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=66745ef2-a61f-414e-a109-1bce2e4c0a52 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  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
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1951879/+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 1951855] Re: Google Chrome freezes the system

[Daniel van Vugt]

This is probably related to memory usage. Please check the memory usage
of the Chrome processes:

  ps -axo rss,cmd | grep chrome | awk '{ total += $1; } END {
printf("Total %.2f GB\n", total/1048576)}'

And if you have any more concerns that are specific to Chrome then you
can report bugs about it to:

  https://bugs.chromium.org/p/chromium/issues/list

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

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

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

Title:
  Google Chrome freezes the system

Status in Ubuntu:
  Invalid

Bug description:
  When I have 10+ tabs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 22 18:20:04 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:146d]
  InstallationDate: Installed on 2021-01-18 (308 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP ProBook 6450b
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=UUID=a01fe12d-3bd8-4fdf-ba27-620f6b5b43ec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2011
  dmi.bios.release: 15.32
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CDE Ver. F.20
  dmi.board.name: 146D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 73.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 115.20
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CDEVer.F.20:bd09/02/2011:br15.32:efr115.20:svnHewlett-Packard:pnHPProBook6450b:pvr:skuWD777EA#AK8:rvnHewlett-Packard:rn146D:rvrKBCVersion73.14:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 6450b
  dmi.product.sku: WD777EA#AK8
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.4
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  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/1951855/+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 1820883] Re: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"]

[Daniel van Vugt]

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

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  totem comma key does not go 1 frame back ["gst_segment_do_seek:
  assertion 'start <= stop' failed"]

Status in gst-plugins-good:
  New
Status in gstreamer1.0 package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  According help the ',' (comma) key should go 1 frame back.
  I press the ',' key once: nothing happens; press again goes forward to end 
video
  after pressing ',' the '.' (dot) key does nothing but i have a message: 
  (totem:31585): GStreamer-CRITICAL **: 18:15:31.465: gst_segment_do_seek: 
assertion 'start <= stop' failed
  pressing dot again it goes 1 frame forward

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 19 18:17:34 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2019-03-14 (5 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190314)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/1820883/+subscriptions


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

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

[Daniel van Vugt]

I don't see any fix on the way. If you're affected by this bug then
please also subscribe to
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

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

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

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

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

  ---

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

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

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

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

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


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

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

[Jason Liu]

Confirmed that this is still an issue in focal.

It is only an issue if I log onto a XFCE session and then log out, these two 
processes stay around:
/usr/libexec/geoclue-2.0/demos/agent
/usr/bin/python3 /usr/share/system-config-printer/applet.py

When I remove the geoclue-2.0 from the system:
sudo apt -y purge geoclue-2.0 --autoremove
The issue no longer shows up. I don't see neither processes hanging around any 
more.

I think those two are related to the two autostart programs:
/etc/xdg/autostart/geoclue-demo-agent.desktop
/etc/xdg/autostart/print-applet.desktop

I think in terms of workaround, two options here:
1. remove geoclue - but the catch here is that if you autoremove, gnome 
dependencies may get removed, which could have unexpected outcome
2. remove autostart files

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

Title:
  "systemd --user" and child processes fail to exit when user logs out

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This concerns systemd 245.2-1ubuntu2 in Ubuntu focal.

  I am using the Xfce desktop. After the user logs out from a desktop
  session, numerous desktop-related processes are left over. Here is a
  listing, taken over twenty minutes after logout:

  skunk853  0.0  0.2  18912 10300 ?Ss   17:55   0:00 
/lib/systemd/systemd --user
  skunk854  0.0  0.0 103304  3496 ?S17:55   0:00 (sd-pam)
  skunk881  0.0  0.1   8076  5324 ?Ss   17:55   0:00 
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
  skunk970  0.0  0.1 305364  6776 ?Ssl  17:55   0:00 
/usr/libexec/at-spi-bus-launcher
  skunk975  0.0  0.1   7352  4452 ?S17:55   0:00 
/usr/bin/dbus-daemon 
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork 
--print-address 3
  skunk979  0.0  0.1 230196  5900 ?Sl   17:55   0:00 
/usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd
  skunk992  0.0  0.1 239704  7676 ?Ssl  17:55   0:00 
/usr/libexec/gvfsd
  skunk997  0.0  0.1 378332  6444 ?Sl   17:55   0:00 
/usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
  skunk   1133  0.0  0.1 156116  5596 ?Sl   17:56   0:00 
/usr/libexec/dconf-service
  skunk   1139  0.0  0.1 236884  4828 ?Sl   17:56   0:00 
/usr/libexec/geoclue-2.0/demos/agent
  skunk   1186  0.0  0.8  59324 34792 ?S17:56   0:00 
/usr/bin/python3 /usr/share/system-config-printer/applet.py
  skunk   1201  0.0  0.6 391676 25688 ?Ssl  17:56   0:00 
/usr/libexec/evolution-source-registry
  skunk   1224  0.0  0.8 616644 35492 ?Sl   17:56   0:00 
/usr/libexec/goa-daemon
  skunk   1235  0.0  0.7 708928 30512 ?Ssl  17:56   0:00 
/usr/libexec/evolution-calendar-factory
  skunk   1243  0.0  0.2 314744  8980 ?Sl   17:56   0:00 
/usr/libexec/goa-identity-service
  skunk   1271  0.0  0.7 681460 29344 ?Ssl  17:56   0:00 
/usr/libexec/evolution-addressbook-factory
  skunk   1302  0.0  0.1  43968  6432 ?Ss   17:56   0:00 
/usr/lib/bluetooth/obexd
  skunk   1322  0.0  0.2 313872  9076 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-udisks2-volume-monitor
  skunk   1327  0.0  0.1 235684  6468 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-mtp-volume-monitor
  skunk   1331  0.0  0.1 237956  6876 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-gphoto2-volume-monitor
  skunk   1335  0.0  0.1 235864  5760 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-goa-volume-monitor
  skunk   1339  0.0  0.2 316716  8800 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-afc-volume-monitor
  skunk   1347  0.0  0.1 313684  7836 ?Sl   17:56   0:00 
/usr/libexec/gvfsd-trash --spawner :1.13 /org/gtk/gvfs/exec_spaw/0
  skunk   1353  0.0  0.1 162128  6028 ?Ssl  17:56   0:00 
/usr/libexec/gvfsd-metadata

  
  When a user logs out of the system, all processes associated with the login 
session should be terminated (barring the use of nohup(1) or the like).

  If I sent a SIGINT to the "systemd --user" process above (PID 853),
  then all the processes promptly go away. This needs to occur on
  logout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+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 1951877] Re: FTBFS - python-testtools does not support Python 3.10

[Athos Ribeiro]

I created an MP with the upstream fix at
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/python-
testtools/+git/python-testtools/+merge/412239

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

Title:
  FTBFS - python-testtools does not support Python 3.10

Status in python-testtools package in Ubuntu:
  New

Bug description:
  As shown in

  https://launchpadlibrarian.net/569859852/buildlog_ubuntu-jammy-
  amd64.python-testtools_2.5.0-2_BUILDING.txt.gz

  python-testtools does not support Python 3.10, and FTBFS for jammy.

  + PYTHONPATH=/<> PYTHON=python3.10 python3.10 -m testtools.run 
testtools.tests.test_suite
  /usr/lib/python3.10/runpy.py:126: RuntimeWarning: 'testtools.run' found in 
sys.modules after import of package 'testtools', but prior to execution of 
'testtools.run'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
  No entry for terminal type "unknown";
  using dumb terminal settings.
  Tests running...
  ==
  FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error
  --
  Traceback (most recent call last):
File "/<>/testtools/tests/test_testresult.py", line 2676, in 
test_syntax_error
  self.assertIn(self._as_output(
File "/<>/testtools/testcase.py", line 399, in assertIn
  self.assertThat(haystack, Contains(needle), message)
File "/<>/testtools/testcase.py", line 480, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, 
b c)\n ^\nSyntaxError: ' not in 'Tests 
running...\n==\nERROR:
 
test_syntax_error.Test.runTest\n--\nTraceback
 (most recent call last):\n  File 
"/tmp/TestNonAsciiResultsa_jvxgt3/test_syntax_error.py", line 6, in runTest\n   
 exec (\'f(a, b c)\')\n  File "", line 1\nf(a, b c)\n 
^^^\nSyntaxError: invalid syntax. Perhaps you forgot a comma?\n\nRan 1 test in 
0.001s\nFAILED (failures=1)\n'
  ==
  FAIL: 
testtools.tests.test_testresult.TestNonAsciiResultsWithUnittest.test_syntax_error
  --
  Traceback (most recent call last):
File "/<>/testtools/tests/test_testresult.py", line 2676, in 
test_syntax_error
  self.assertIn(self._as_output(
File "/<>/testtools/testcase.py", line 399, in assertIn
  self.assertThat(haystack, Contains(needle), message)
File "/<>/testtools/testcase.py", line 480, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, 
b c)\n ^\nSyntaxError: ' not in 
'E\n==\nERROR:
 runTest 
(test_syntax_error.Test)\ntest_syntax_error.Test.runTest\n--\ntesttools.testresult.real._StringException:
 Traceback (most recent call last):\n  File 
"/tmp/TestNonAsciiResultsWithUnittest3zrnkc8g/test_syntax_error.py", line 6, in 
runTest\nexec (\'f(a, b c)\')\n  File "", line 1\nf(a, b c)\n   
  ^^^\nSyntaxError: invalid syntax. Perhaps you forgot a 
comma?\n\n\n--\nRan
 1 test in 0.000s\n\nFAILED (errors=1)\n'

  Ran 2625 tests in 1.221s
  FAILED (failures=2)
  make[1]: *** [debian/rules:36: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:10: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
  

  Build finished at 2021-11-20T06:46:48Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1951877/+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 1951879] [NEW] System freezes

[Philippe Comte]

Public bug reported:

The problem can be reproduced as follow in ubuntu 21.10:
- run jedit (which was insalled with sudo apt install jedit)
- jedit starts and is working fine, but a right click on its icon in the dock 
freezes the system
- it is still possible to log into the system using ssh and I noticed that 
gnome-shell is using 100% of a CPU.
- the system does not recover without shutting it down and restarting it
- the problem could be reproduced on a lenovo laptop as well as in a VM

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 22 21:24:51 2021
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2021-11-22 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=66745ef2-a61f-414e-a109-1bce2e4c0a52 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
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
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug freeze impish ubuntu wayland-session

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

Title:
  System freezes

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem can be reproduced as follow in ubuntu 21.10:
  - run jedit (which was insalled with sudo apt install jedit)
  - jedit starts and is working fine, but a right click on its icon in the dock 
freezes the system
  - it is still possible to log into the system using ssh and I noticed that 
gnome-shell is using 100% of a CPU.
  - the system does not recover without shutting it down and restarting it
  - the problem could be reproduced on a lenovo laptop as well as in a VM

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 22 21:24:51 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2021-11-22 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root 

[Touch-packages] [Bug 1951877] Re: FTBFS - python-testtools does not support Python 3.10

[Athos Ribeiro]

Forwarded a fix to Debian in https://salsa.debian.org/openstack-
team/python/python-testtools/-/merge_requests/5

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

Title:
  FTBFS - python-testtools does not support Python 3.10

Status in python-testtools package in Ubuntu:
  New

Bug description:
  As shown in

  https://launchpadlibrarian.net/569859852/buildlog_ubuntu-jammy-
  amd64.python-testtools_2.5.0-2_BUILDING.txt.gz

  python-testtools does not support Python 3.10, and FTBFS for jammy.

  + PYTHONPATH=/<> PYTHON=python3.10 python3.10 -m testtools.run 
testtools.tests.test_suite
  /usr/lib/python3.10/runpy.py:126: RuntimeWarning: 'testtools.run' found in 
sys.modules after import of package 'testtools', but prior to execution of 
'testtools.run'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
  No entry for terminal type "unknown";
  using dumb terminal settings.
  Tests running...
  ==
  FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error
  --
  Traceback (most recent call last):
File "/<>/testtools/tests/test_testresult.py", line 2676, in 
test_syntax_error
  self.assertIn(self._as_output(
File "/<>/testtools/testcase.py", line 399, in assertIn
  self.assertThat(haystack, Contains(needle), message)
File "/<>/testtools/testcase.py", line 480, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, 
b c)\n ^\nSyntaxError: ' not in 'Tests 
running...\n==\nERROR:
 
test_syntax_error.Test.runTest\n--\nTraceback
 (most recent call last):\n  File 
"/tmp/TestNonAsciiResultsa_jvxgt3/test_syntax_error.py", line 6, in runTest\n   
 exec (\'f(a, b c)\')\n  File "", line 1\nf(a, b c)\n 
^^^\nSyntaxError: invalid syntax. Perhaps you forgot a comma?\n\nRan 1 test in 
0.001s\nFAILED (failures=1)\n'
  ==
  FAIL: 
testtools.tests.test_testresult.TestNonAsciiResultsWithUnittest.test_syntax_error
  --
  Traceback (most recent call last):
File "/<>/testtools/tests/test_testresult.py", line 2676, in 
test_syntax_error
  self.assertIn(self._as_output(
File "/<>/testtools/testcase.py", line 399, in assertIn
  self.assertThat(haystack, Contains(needle), message)
File "/<>/testtools/testcase.py", line 480, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, 
b c)\n ^\nSyntaxError: ' not in 
'E\n==\nERROR:
 runTest 
(test_syntax_error.Test)\ntest_syntax_error.Test.runTest\n--\ntesttools.testresult.real._StringException:
 Traceback (most recent call last):\n  File 
"/tmp/TestNonAsciiResultsWithUnittest3zrnkc8g/test_syntax_error.py", line 6, in 
runTest\nexec (\'f(a, b c)\')\n  File "", line 1\nf(a, b c)\n   
  ^^^\nSyntaxError: invalid syntax. Perhaps you forgot a 
comma?\n\n\n--\nRan
 1 test in 0.000s\n\nFAILED (errors=1)\n'

  Ran 2625 tests in 1.221s
  FAILED (failures=2)
  make[1]: *** [debian/rules:36: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:10: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
  

  Build finished at 2021-11-20T06:46:48Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1951877/+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 1950521] Re: testresources does not support python 3.10

[Athos Ribeiro]

Thanks, Brian!

I am marking python-testtools as invalid in favor of
https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1951877

** Changed in: python-testtools (Ubuntu)
   Status: New => Invalid

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

Title:
  testresources does not support python 3.10

Status in python-gear package in Ubuntu:
  New
Status in python-launchpadlib package in Ubuntu:
  Fix Released
Status in python-testtools package in Ubuntu:
  Invalid
Status in testresources package in Ubuntu:
  Fix Released

Bug description:
  testresources does not support Python 3.10. The package cannot be
  loaded due to an incompatibility in the package's __init__.py file, as
  shown in [1], which is a fix proposed upstream.

  [1] https://github.com/testing-cabal/testresources/pull/14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-gear/+bug/1950521/+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 1951877] [NEW] FTBFS - python-testtools does not support Python 3.10

[Athos Ribeiro]

Public bug reported:

As shown in

https://launchpadlibrarian.net/569859852/buildlog_ubuntu-jammy-
amd64.python-testtools_2.5.0-2_BUILDING.txt.gz

python-testtools does not support Python 3.10, and FTBFS for jammy.

+ PYTHONPATH=/<> PYTHON=python3.10 python3.10 -m testtools.run 
testtools.tests.test_suite
/usr/lib/python3.10/runpy.py:126: RuntimeWarning: 'testtools.run' found in 
sys.modules after import of package 'testtools', but prior to execution of 
'testtools.run'; this may result in unpredictable behaviour
  warn(RuntimeWarning(msg))
No entry for terminal type "unknown";
using dumb terminal settings.
Tests running...
==
FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error
--
Traceback (most recent call last):
  File "/<>/testtools/tests/test_testresult.py", line 2676, in 
test_syntax_error
self.assertIn(self._as_output(
  File "/<>/testtools/testcase.py", line 399, in assertIn
self.assertThat(haystack, Contains(needle), message)
  File "/<>/testtools/testcase.py", line 480, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, b 
c)\n ^\nSyntaxError: ' not in 'Tests 
running...\n==\nERROR:
 
test_syntax_error.Test.runTest\n--\nTraceback
 (most recent call last):\n  File 
"/tmp/TestNonAsciiResultsa_jvxgt3/test_syntax_error.py", line 6, in runTest\n   
 exec (\'f(a, b c)\')\n  File "", line 1\nf(a, b c)\n 
^^^\nSyntaxError: invalid syntax. Perhaps you forgot a comma?\n\nRan 1 test in 
0.001s\nFAILED (failures=1)\n'
==
FAIL: 
testtools.tests.test_testresult.TestNonAsciiResultsWithUnittest.test_syntax_error
--
Traceback (most recent call last):
  File "/<>/testtools/tests/test_testresult.py", line 2676, in 
test_syntax_error
self.assertIn(self._as_output(
  File "/<>/testtools/testcase.py", line 399, in assertIn
self.assertThat(haystack, Contains(needle), message)
  File "/<>/testtools/testcase.py", line 480, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, b 
c)\n ^\nSyntaxError: ' not in 
'E\n==\nERROR:
 runTest 
(test_syntax_error.Test)\ntest_syntax_error.Test.runTest\n--\ntesttools.testresult.real._StringException:
 Traceback (most recent call last):\n  File 
"/tmp/TestNonAsciiResultsWithUnittest3zrnkc8g/test_syntax_error.py", line 6, in 
runTest\nexec (\'f(a, b c)\')\n  File "", line 1\nf(a, b c)\n   
  ^^^\nSyntaxError: invalid syntax. Perhaps you forgot a 
comma?\n\n\n--\nRan
 1 test in 0.000s\n\nFAILED (errors=1)\n'

Ran 2625 tests in 1.221s
FAILED (failures=2)
make[1]: *** [debian/rules:36: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Build finished at 2021-11-20T06:46:48Z

** Affects: python-testtools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: ftbfs update-excuse

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

Title:
  FTBFS - python-testtools does not support Python 3.10

Status in python-testtools package in Ubuntu:
  New

Bug description:
  As shown in

  https://launchpadlibrarian.net/569859852/buildlog_ubuntu-jammy-
  amd64.python-testtools_2.5.0-2_BUILDING.txt.gz

  python-testtools does not support Python 3.10, and FTBFS for jammy.

  + PYTHONPATH=/<> PYTHON=python3.10 python3.10 -m testtools.run 
testtools.tests.test_suite
  /usr/lib/python3.10/runpy.py:126: RuntimeWarning: 'testtools.run' found in 
sys.modules after import of package 'testtools', but prior to execution of 
'testtools.run'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
  No entry for terminal type "unknown";
  using dumb terminal settings.
  Tests running...
  ==
  FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error
  --
  Traceback (most recent call last):
File "/<>/testtools/tests/test_testresult.py", line 2676, in 
test_syntax_error
  

[Touch-packages] [Bug 1950521] Re: testresources does not support python 3.10

[Athos Ribeiro]

** Changed in: python-launchpadlib (Ubuntu)
   Status: New => Fix Released

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

Title:
  testresources does not support python 3.10

Status in python-gear package in Ubuntu:
  New
Status in python-launchpadlib package in Ubuntu:
  Fix Released
Status in python-testtools package in Ubuntu:
  New
Status in testresources package in Ubuntu:
  Fix Released

Bug description:
  testresources does not support Python 3.10. The package cannot be
  loaded due to an incompatibility in the package's __init__.py file, as
  shown in [1], which is a fix proposed upstream.

  [1] https://github.com/testing-cabal/testresources/pull/14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-gear/+bug/1950521/+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 1820883] Re: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"]

[corrado venturini]

Problem not reproducible with totem 3.38.2-1ubuntu1

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

Title:
  totem comma key does not go 1 frame back ["gst_segment_do_seek:
  assertion 'start <= stop' failed"]

Status in gst-plugins-good:
  New
Status in gstreamer1.0 package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Triaged

Bug description:
  According help the ',' (comma) key should go 1 frame back.
  I press the ',' key once: nothing happens; press again goes forward to end 
video
  after pressing ',' the '.' (dot) key does nothing but i have a message: 
  (totem:31585): GStreamer-CRITICAL **: 18:15:31.465: gst_segment_do_seek: 
assertion 'start <= stop' failed
  pressing dot again it goes 1 frame forward

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 19 18:17:34 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2019-03-14 (5 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190314)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/1820883/+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 1951827] Re: APT crashes with Segmentation fault

[Julian Andres Klode]

This is the Ubuntu bug tracker, to report bugs in Debian, please follow the 
Debian bug reporting instructions at https://www.debian.org/Bugs/Reporting. 
When submitting the bug to Debian, you'll need to provide a gdb backtrace,
a core file, and instructions to reproduce the issue.

If "Debian 10" was a mistake, please run apport-collect 1951827 after
such a crash to collect data on this bug, and update the bug with
instructions as to how the bug can be reproduced.

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

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

Title:
  APT crashes with Segmentation fault

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  **System:**

  - OS Type: Linux

  - OS: Debian 10

  - APT / APT-utils version: 2.24

  
  **Bug description:**

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

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


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

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

[Brian Murray]

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

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

Title:
  APT crashes with Segmentation fault

Status in apt package in Ubuntu:
  New

Bug description:
  **System:**

  - OS Type: Linux

  - OS: Debian 10

  - APT / APT-utils version: 2.24

  
  **Bug description:**

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

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


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

[Touch-packages] [Bug 1951867] [NEW] python3-opencv fails to install due to unmet dependency.

[spec]

Public bug reported:

1)
Description:Ubuntu 20.04.3 LTS
Release:20.04

2)
python3-opencv:
  Installed: (none)
  Candidate: 4.2.0+dfsg-5
  Version table:
 4.2.0+dfsg-5 500
500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

3) I expected 'apt install python3-opencv` to complete without issue.

4)
Issuing:  'apt install python3-opencv` fails with:

"Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3-opencv : Depends: libopencv-dnn4.2 (= 4.2.0+dfsg-5+20.04.sav2) but it 
is not going to be installed
  Depends: libopencv-superres4.2 (= 4.2.0+dfsg-5+20.04.sav2) 
but it is not going to be installed
  Depends: libopencv-contrib4.2 (>= 4.2.0+dfsg) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages."


Drilling down, 'libopencv-dnn4.2' requires 'libprotobuf23' which is not 
available for 20.04, but is available for 20.10.

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

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

Title:
  python3-opencv fails to install due to unmet dependency.

Status in opencv package in Ubuntu:
  New

Bug description:
  1)
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  2)
  python3-opencv:
Installed: (none)
Candidate: 4.2.0+dfsg-5
Version table:
   4.2.0+dfsg-5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

  3) I expected 'apt install python3-opencv` to complete without issue.

  4)
  Issuing:  'apt install python3-opencv` fails with:

  "Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   python3-opencv : Depends: libopencv-dnn4.2 (= 4.2.0+dfsg-5+20.04.sav2) but 
it is not going to be installed
Depends: libopencv-superres4.2 (= 4.2.0+dfsg-5+20.04.sav2) 
but it is not going to be installed
Depends: libopencv-contrib4.2 (>= 4.2.0+dfsg) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages."

  
  Drilling down, 'libopencv-dnn4.2' requires 'libprotobuf23' which is not 
available for 20.04, but is available for 20.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1951867/+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 1951827] [NEW] APT crashes with Segmentation fault

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

**System:**

- OS Type: Linux

- OS: Debian 10

- APT / APT-utils version: 2.24


**Bug description:**

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

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


** Tags: bot-comment
-- 
APT crashes with Segmentation fault
https://bugs.launchpad.net/bugs/1951827
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt 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 1951855] [NEW] Google Chrome freezes the system

[Pavlo Protsenko]

Public bug reported:

When I have 10+ tabs

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-40-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 22 18:20:04 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:146d]
InstallationDate: Installed on 2021-01-18 (308 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Hewlett-Packard HP ProBook 6450b
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=UUID=a01fe12d-3bd8-4fdf-ba27-620f6b5b43ec ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/02/2011
dmi.bios.release: 15.32
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CDE Ver. F.20
dmi.board.name: 146D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 73.14
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 115.20
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CDEVer.F.20:bd09/02/2011:br15.32:efr115.20:svnHewlett-Packard:pnHPProBook6450b:pvr:skuWD777EA#AK8:rvnHewlett-Packard:rn146D:rvrKBCVersion73.14:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP ProBook 6450b
dmi.product.sku: WD777EA#AK8
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.4
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.4
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
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

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu wayland-session

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

Title:
  Google Chrome freezes the system

Status in xorg package in Ubuntu:
  New

Bug description:
  When I have 10+ tabs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 22 18:20:04 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:146d]
  InstallationDate: Installed on 2021-01-18 (308 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP ProBook 6450b
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=UUID=a01fe12d-3bd8-4fdf-ba27-620f6b5b43ec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2011
  dmi.bios.release: 15.32
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CDE Ver. F.20
  dmi.board.name: 146D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 73.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 115.20
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CDEVer.F.20:bd09/02/2011:br15.32:efr115.20:svnHewlett-Packard:pnHPProBook6450b:pvr:skuWD777EA#AK8:rvnHewlett-Packard:rn146D:rvrKBCVersion73.14:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 6450b
  dmi.product.sku: WD777EA#AK8
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: 

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

[paquin pierre]

Hello Daniel,

So far I still have the issue on Ubuntu 20.04 LTS. Can you tell me if
the patch will be in next 22.04 LTS ? Or maybe there's a way to patch
20.04?

Thanks,

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

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

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

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

  ---

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

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

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

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

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


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

[Touch-packages] [Bug 1627564] Re: Various apps crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493/494]

[BobbitStephane]

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

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

Title:
  Various apps crash due to assertion failure in
  ensure_surface_for_gicon [gtkiconhelper.c:493/494]

Status in GTK+:
  Unknown
Status in debconf package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in debconf source package in Focal:
  Confirmed
Status in gtk+3.0 source package in Focal:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
  https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383
  https://errors.ubuntu.com/problem/519aee3ed0c68efc5b754ee3e783103e59361d46

  ---

  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1627564/+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 1950794] Re: DHCPv4 (IAID+DUID) networking broken in LXC containers

[Lukas Märdian]

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

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

Title:
  DHCPv4 (IAID+DUID) networking broken in LXC containers

Status in lxd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  DHCPv4 networking does not work in the default IAID+DUID
  (ClientIdentifier=duid) mode in LXC containers, using systemd-networkd
  v249.5-2ubuntu1. Static configuration and DHCPv6 work without problem.

  Reproducer:
  $ lxc launch ubuntu-daily:jammy jj
  $ lxc exec jj bash
  # add-apt-repository ppa:ci-train-ppa-service/4704
  # apt install systemd # install systemd 249.5-2ubuntu1
  # cat /etc/systemd/network/00-test.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  # systemctl restart systemd-networkd.service
  # networkctl 
  IDX LINK TYPE OPERATIONAL SETUP
  [...]
  611 eth0 ethercarrier failed  

  A workaround is to avoid IAID+DUID mode via:
  [DHCPv4]
  #ClientIdentifier=mac
  ClientIdentifier=duid-only

  Interesting logs:
  Nov 12 14:10:48 jj systemd-networkd[174]: eth0: Requested to activate link
  Nov 12 14:10:48 jj systemd-networkd[174]: eth0: DHCPv4 client: Failed to set 
IAID: Device or resource busy
  Nov 12 14:10:48 jj systemd-networkd[174]: eth0: DHCP4 CLIENT: Failed to set 
IAID+DUID: Device or resource busy
  Nov 12 14:10:48 jj systemd-networkd[174]: Failed to check link is 
initialized: Device or resource busy
  Nov 12 14:10:48 jj systemd-networkd[174]: eth0: Failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1950794/+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 1951727] Re: Sync libsemanage 3.3-1 (main) from Debian unstable (main)

[Sebastien Bacher]

This bug was fixed in the package libsemanage - 3.3-1
Sponsored for Rico Tzschichholz (ricotz)

---
libsemanage (3.3-1) unstable; urgency=medium

  [ Christian Göttsche ]
  * d/gitlab-ci.yml: Use Debian recipe
  * d/control: Bump debhelper compat to level 13
  * d/control: Bump Standards-Version to 4.5.1 (no further changes)
  * d/control: Update homepage
  * d/rules: Enable build hardening
  * d/rules: Enable -Wall -Wextra
  * d/control: Convert cute fields
  * d/control: Declare semanage-utils Architecture all

  [ Laurent Bigonville ]
  * debian/control: Properly depend against libsepol2 instead of libsepol1
  * New upstream version 3.3
- debian/control: Bump {build-}dependencies to match new release
  * debian/control: Bump Standards-Version to 4.6.0 (no further changes)
  * debian/control: Relax the versioned dependency against -common a bit

 -- Laurent Bigonville   Mon, 08 Nov 2021 15:01:36
+0100

libsemanage (3.2-1) experimental; urgency=medium

  * New upstream version
- debian/control: Bump {build-}dependencies to match new release
- Bump the soname from 1 to 2, drop the soname from the -dev package
  * debian/watch: Update the URL to follow the new tagging format
  * debian/control: Drop ancients Breaks against selinux-policy-default and
selinux-policy-mls
  * debian/patches/fix_tests.patch: Add the Forwarded tag to please lintian

 -- Laurent Bigonville   Sat, 24 Apr 2021 13:52:18
+0200

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

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

Title:
  Sync libsemanage 3.3-1 (main) from Debian unstable (main)

Status in libsemanage package in Ubuntu:
  Fix Released

Bug description:
  Please sync libsemanage 3.3-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Don't build with lto. Fedora has a patch enabling this, but also
  removing some symbols.

  This new upstream version builds without errors.

  Changelog entries since current jammy version 3.1-1ubuntu3:

  libsemanage (3.3-1) unstable; urgency=medium

[ Christian Göttsche ]
* d/gitlab-ci.yml: Use Debian recipe
* d/control: Bump debhelper compat to level 13
* d/control: Bump Standards-Version to 4.5.1 (no further changes)
* d/control: Update homepage
* d/rules: Enable build hardening
* d/rules: Enable -Wall -Wextra
* d/control: Convert cute fields
* d/control: Declare semanage-utils Architecture all

[ Laurent Bigonville ]
* debian/control: Properly depend against libsepol2 instead of libsepol1
* New upstream version 3.3
  - debian/control: Bump {build-}dependencies to match new release
* debian/control: Bump Standards-Version to 4.6.0 (no further changes)
* debian/control: Relax the versioned dependency against -common a bit

   -- Laurent Bigonville   Mon, 08 Nov 2021 15:01:36
  +0100

  libsemanage (3.2-1) experimental; urgency=medium

* New upstream version
  - debian/control: Bump {build-}dependencies to match new release
  - Bump the soname from 1 to 2, drop the soname from the -dev package
* debian/watch: Update the URL to follow the new tagging format
* debian/control: Drop ancients Breaks against selinux-policy-default and
  selinux-policy-mls
* debian/patches/fix_tests.patch: Add the Forwarded tag to please lintian

   -- Laurent Bigonville   Sat, 24 Apr 2021 13:52:18
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsemanage/+bug/1951727/+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 1942799] Re: Exiv2 creates out of range exception with XMP data

[Hans Bull]

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

** This bug has been marked a duplicate of bug 1941752
   Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images 
exported by darktable

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

Title:
  Exiv2 creates out of range exception with XMP data

Status in exiv2 package in Ubuntu:
  Confirmed

Bug description:
  Applying the latest update to Exiv2 in both Pix and gThumb, images
  that contain XMP data will crash the given application. The issue
  looks to be when Xmp data is not able to properly handle the call to
  "c_str()".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1942799/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable

[Hans Bull]

Fixed upstream on Sept, 22:
https://github.com/Exiv2/exiv2/commit/8a1e949bff482f74599f60b8ab518442036b1834#diff-b28a1f0018497d794db6df47daa5413371c3e933681f9c126d447f90d30084d8

How long will we have to wait to see this fixed in the Ubuntu
repositories? This is a real showstopper bug.

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Unknown
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1920836] Re: Show Extended Security Maintenence status

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.32.18

---
software-properties (0.96.24.32.18) bionic; urgency=medium

  [ Chad Smith ]
  * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status
- Handle absent /var/lib/ubuntu-advantage/status.json for non-root
  users (LP: #1939732)
- print unexpected errors and if _schema_version not equal to 0.1

software-properties (0.96.24.32.17) bionic; urgency=medium

  * Show Ubuntu Pro banner on Livepatch page (LP: #1934439)

 -- Robert Ancell   Fri, 05 Nov 2021
16:44:17 +1300

** Changed in: software-properties (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Show Extended Security Maintenence status

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  Fix Released
Status in software-properties source package in Focal:
  Fix Released
Status in software-properties source package in Hirsute:
  Fix Released
Status in software-properties source package in Impish:
  Fix Released

Bug description:
  [Impact]
  There is not currently a graphical method of determining if a system is 
subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) 
updates. This is resolved by adding some [new 
UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to 
the software properties application.

  [Test Case]
  1. Install latest version of Ubuntu advantage:
  $ sudo add-apt-repository ppa:ua-client/stable
  $ sudo apt update
  $ sudo apt upgrade
  2. Open Software Properties
  3. Go to Updates tab.

  Expected result:
  Information is shown that indicates if this system is using Extended Security 
Maintenance updates, when updates will supported until, and a link to upgrade 
to ESM.

  Observed result:
  No ESM information currently shown.

  [Where problems could occur]
  - Software properties could hit a bug getting a response from the ua app. The 
current code carefully checks if and what is returned, falling back to a safe 
default behavior.
  - Launching software properties could trigger a bug in the ua app.
  - Software properties could show incorrect information, causing confusion for 
the user. The solution uses information from distro-info and the ua app which 
means software-properties contains no data about ESM, and instead relies on 
these apps that can be updated if things change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+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 1934439] Re: Add Ubuntu Pro banner to Livepatch page

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.32.18

---
software-properties (0.96.24.32.18) bionic; urgency=medium

  [ Chad Smith ]
  * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status
- Handle absent /var/lib/ubuntu-advantage/status.json for non-root
  users (LP: #1939732)
- print unexpected errors and if _schema_version not equal to 0.1

software-properties (0.96.24.32.17) bionic; urgency=medium

  * Show Ubuntu Pro banner on Livepatch page (LP: #1934439)

 -- Robert Ancell   Fri, 05 Nov 2021
16:44:17 +1300

** Changed in: software-properties (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Add Ubuntu Pro banner to Livepatch page

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  Fix Released
Status in software-properties source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for 
Desktop. Note that this is not shown in current releases, as this feature only 
applies to older versions.

  [Test Case]
  1. Open Software Properties.
  2. Go to Livepatch tab.
  Expected result:
  A banner is shown directing the user to Ubuntu Pro.
  The banner can be dismissed, and doesn't return when restarting 
software-properties.

  [Regression Potential]
  Some risk of introducing a new bug, however the change is quite small and 
doesn't have any complex interactions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.32.18

---
software-properties (0.96.24.32.18) bionic; urgency=medium

  [ Chad Smith ]
  * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status
- Handle absent /var/lib/ubuntu-advantage/status.json for non-root
  users (LP: #1939732)
- print unexpected errors and if _schema_version not equal to 0.1

software-properties (0.96.24.32.17) bionic; urgency=medium

  * Show Ubuntu Pro banner on Livepatch page (LP: #1934439)

 -- Robert Ancell   Fri, 05 Nov 2021
16:44:17 +1300

** Changed in: software-properties (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  report availability of Ubuntu Advantage ESM services on unattached
  machines

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Released
Status in software-properties source package in Focal:
  Fix Released
Status in software-properties source package in Hirsute:
  Fix Released
Status in software-properties source package in Impish:
  Fix Released

Bug description:
  [Impact]

    * Error messages emitted to software-properties-gtk console "[Errno 2] No 
such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to 
incorrect expectation that status.json file is written when non-root runs `ua 
status`
    * This logic results in multiple `ua status` calls which each result in a 
network-egress to https://contracts.canonical.com on unattached machines which 
could result in delays in rendering  the GTK dialogs while awaiting a response.

  [Test Case]
  1. Install latest version of software-properties-gtk from -proposed
  cat > setup_proposed.sh 

[Touch-packages] [Bug 1943109] Re: Merge 1.1.1l-1 version from Debian

[Simon Chopin]

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

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

Title:
  Merge 1.1.1l-1 version from Debian

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  This new upstream version consists only of a couple security fixes,
  and should thus be merged into Impish.

  Upstream changelog:

   Changes between 1.1.1k and 1.1.1l [24 Aug 2021]

*) Fixed an SM2 Decryption Buffer Overflow.

   In order to decrypt SM2 encrypted data an application is expected to 
call the
   API function EVP_PKEY_decrypt(). Typically an application will call this
   function twice. The first time, on entry, the "out" parameter can be 
NULL and,
   on exit, the "outlen" parameter is populated with the buffer size 
required to
   hold the decrypted plaintext. The application can then allocate a 
sufficiently
   sized buffer and call EVP_PKEY_decrypt() again, but this time passing a 
non-NULL
   value for the "out" parameter.

   A bug in the implementation of the SM2 decryption code means that the
   calculation of the buffer size required to hold the plaintext returned 
by the
   first call to EVP_PKEY_decrypt() can be smaller than the actual size 
required by
   the second call. This can lead to a buffer overflow when 
EVP_PKEY_decrypt() is
   called by the application a second time with a buffer that is too small.

   A malicious attacker who is able present SM2 content for decryption to an
   application could cause attacker chosen data to overflow the buffer by 
up to a
   maximum of 62 bytes altering the contents of other data held after the
   buffer, possibly changing application behaviour or causing the 
application to
   crash. The location of the buffer is application dependent but is 
typically
   heap allocated.
   (CVE-2021-3711)
   [Matt Caswell]

*) Fixed various read buffer overruns processing ASN.1 strings

   ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING
   structure which contains a buffer holding the string data and a field 
holding
   the buffer length. This contrasts with normal C strings which are 
repesented as
   a buffer for the string data which is terminated with a NUL (0) byte.

   Although not a strict requirement, ASN.1 strings that are parsed using 
OpenSSL's
   own "d2i" functions (and other similar parsing functions) as well as any 
string
   whose value has been set with the ASN1_STRING_set() function will 
additionally
   NUL terminate the byte array in the ASN1_STRING structure.

   However, it is possible for applications to directly construct valid 
ASN1_STRING
   structures which do not NUL terminate the byte array by directly setting 
the
   "data" and "length" fields in the ASN1_STRING array. This can also 
happen by
   using the ASN1_STRING_set0() function.

   Numerous OpenSSL functions that print ASN.1 data have been found to 
assume that
   the ASN1_STRING byte array will be NUL terminated, even though this is 
not
   guaranteed for strings that have been directly constructed. Where an 
application
   requests an ASN.1 structure to be printed, and where that ASN.1 structure
   contains ASN1_STRINGs that have been directly constructed by the 
application
   without NUL terminating the "data" field, then a read buffer overrun can 
occur.

   The same thing can also occur during name constraints processing of 
certificates
   (for example if a certificate has been directly constructed by the 
application
   instead of loading it via the OpenSSL parsing functions, and the 
certificate
   contains non NUL terminated ASN1_STRING structures). It can also occur 
in the
   X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions.

   If a malicious actor can cause an application to directly construct an
   ASN1_STRING and then process it through one of the affected OpenSSL 
functions
   then this issue could be hit. This might result in a crash (causing a 
Denial of
   Service attack). It could also result in the disclosure of private memory
   contents (such as private keys, or sensitive plaintext).
   (CVE-2021-3712)
   [Matt Caswell]

  Debian changelog:

  openssl (1.1.1l-1) unstable; urgency=medium

* New upstream version.
  - CVE-2021-3711 (SM2 Decryption Buffer Overflow).
  - CVE-2021-3712 (Read buffer overruns processing ASN.1 strings).

   -- Sebastian Andrzej Siewior   Wed, 25 Aug
  2021 00:19:05 +0200

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


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