date:20211122

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1950925

Title:
  alt-tab doesnt work anymore after upgrade to 21.10

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I want to swicth windows with alt-tab.

  This worked until before I just upgraded from 21.4 to 21.10.

  Now nothing happens anymore.
  In Settings -> Keyboard -> Customize 
  Shortcuts -> Navigation

  the Shortcut for "Switch Windows" is set to alt-tab, but pressing
  these doesnt do anything.

  Super-Tab works, but it switches applications, not windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 15 00:47:15 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-12 (581 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-11-14 (0 days ago)

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


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

[Desktop-packages] [Bug 1950925] Re: alt-tab doesnt work anymore after upgrade to 21.10

2021-11-22 Thread Joe

Hi all,

This also affects me, starting with the update to 21.04 and continuing
with the 21.10 update. alt does nothing, super switches between
applications. I haven't installed any Gnome extensions.

~$ gsettings get org.gnome.desktop.wm.keybindings switch-applications
['Tab']

~$ gsettings get org.gnome.desktop.wm.keybindings switch-windows
['Tab']

Thank you for the work!!

-Joe

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1950925

Title:
  alt-tab doesnt work anymore after upgrade to 21.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I want to swicth windows with alt-tab.

  This worked until before I just upgraded from 21.4 to 21.10.

  Now nothing happens anymore.
  In Settings -> Keyboard -> Customize 
  Shortcuts -> Navigation

  the Shortcut for "Switch Windows" is set to alt-tab, but pressing
  these doesnt do anything.

  Super-Tab works, but it switches applications, not windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 15 00:47:15 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-12 (581 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-11-14 (0 days ago)

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


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

[Desktop-packages] [Bug 1951139] Re: Alt-tab task switching broken

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

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1951139

Title:
  Alt-tab task switching broken

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Upgraded Ubuntu to 21.10, running Ubuntu on Wayland (the default). Was
  working at first, but this time I booted and ALT+TAB doesn't work. The
  alt and tab keys work in apps, CTRL+TAB works, but ALT+TAB acts as if
  I hit ALT or does nothing at all.

  WIN+TAB does work.

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


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

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

2021-11-22 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly

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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951731] Re: screen freezes for several seconds

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

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

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

** Changed in: gnome-shell-extension-gsconnect (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1951731

Title:
  screen freezes for several seconds

Status in gnome-shell-extension-gsconnect package in Ubuntu:
  New

Bug description:
  AMD graphics
  screen freezes for several seconds until it freezes completely

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 21 13:37:32 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-05-28 (176 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1632529] Re: sound problem

[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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1944667] Re: High CPU usage in Xorg with NVIDIA reverse prime external monitor

[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1944667

Title:
  High CPU usage in Xorg with NVIDIA reverse prime external monitor

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Expired
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Expired

Bug description:
  With my Legion Slim 7 in hybrid graphics mode (using amdgpu to drive
  the laptop display) and an external monitor connected via the nvidia
  card on a USB-C/HDMI connection, Xorg consistently uses around 40% CPU
  even with no apps running.

  If I put the laptop in discrete graphics mode so the nvidia card
  drives both the laptop display and the external monitor Xorg uses
  close to 0% CPU, which is what I would expect it to be in hybrid mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xserver-xorg-core 2:1.20.13-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.63.01  Tue Aug  3 
20:44:16 UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Thu Sep 23 11:48:15 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.63.01, 5.13.0-16-generic, x86_64: installed
   nvidia, 470.63.01, 5.14.5-051405-generic, x86_64: installed
   nvidia, 470.63.01, 5.15.0-051500rc2-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3801]
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:380c]
  InstallationDate: Installed on 2021-09-15 (8 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: LENOVO 82K8
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic 
root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet 
splash amdgpu.backlight=0 vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2: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-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1944667/+subscriptions


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

[Desktop-packages] [Bug 1944667] Re: High CPU usage in Xorg with NVIDIA reverse prime external monitor

[Expired for nvidia-graphics-drivers-470 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1944667

Title:
  High CPU usage in Xorg with NVIDIA reverse prime external monitor

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Expired
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Expired

Bug description:
  With my Legion Slim 7 in hybrid graphics mode (using amdgpu to drive
  the laptop display) and an external monitor connected via the nvidia
  card on a USB-C/HDMI connection, Xorg consistently uses around 40% CPU
  even with no apps running.

  If I put the laptop in discrete graphics mode so the nvidia card
  drives both the laptop display and the external monitor Xorg uses
  close to 0% CPU, which is what I would expect it to be in hybrid mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xserver-xorg-core 2:1.20.13-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.63.01  Tue Aug  3 
20:44:16 UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-5ubuntu1)
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Thu Sep 23 11:48:15 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.63.01, 5.13.0-16-generic, x86_64: installed
   nvidia, 470.63.01, 5.14.5-051405-generic, x86_64: installed
   nvidia, 470.63.01, 5.15.0-051500rc2-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3801]
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:380c]
  InstallationDate: Installed on 2021-09-15 (8 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: LENOVO 82K8
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic 
root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet 
splash amdgpu.backlight=0 vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2: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-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1944667/+subscriptions


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

[Desktop-packages] [Bug 1949572] Re: freeze after back-to-back left and right click on the app in the dock

I can reproduce the bug now using jedit (instructions from duplicate bug
1951879).

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => High

** Tags added: jammy

** Summary changed:

- freeze after back-to-back left and right click on the app in the dock
+ Shell freeze after right click on the app in the dock

** Tags added: rls-ii-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1949572

Title:
  Shell freeze after right click on the app in the dock

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

Bug description:
  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  I'm using Ubuntu 21.10. I installed it today.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-03 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1951879] Re: System freezes after right clicking on a dock icon

*** 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. This particular bug has already been reported and is a
duplicate of bug 1949572, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1949572
   freeze after back-to-back left and right click on the app in the dock

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951879] Re: System freezes after right clicking on a dock icon

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

Also, next time the problems happens, after rebooting please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951879] Re: System freezes after right clicking on a dock icon

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

See also bug 1949572 and bug 1947571.

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951879] Re: System freezes after right clicking on a dock icon

*** 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951855] Re: Google Chrome freezes the system

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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1930297] Re: Clipboard sharing is disabled when using RDP backend

2021-11-22 Thread Jeremy Bicha

** Changed in: gnome-remote-desktop (Ubuntu)
   Status: Triaged => Fix Committed

** Tags added: jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1930297

Title:
  Clipboard sharing is disabled when using RDP backend

Status in gnome-remote-desktop package in Ubuntu:
  Fix Committed

Bug description:
  We disabled RDP clipoard as part of gnome-remote-desktop 40.1-1 as it
  requires libfuse-3 to be in main.

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


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

[Desktop-packages] [Bug 1951731] Re: screen freezes for several seconds

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

** This bug has been marked a duplicate of bug 1812892
   Use high ram memory by the gnome-shell-extension-gsconnect

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1951731

Title:
  screen freezes for several seconds

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  AMD graphics
  screen freezes for several seconds until it freezes completely

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 21 13:37:32 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-05-28 (176 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1951072] Re: gnome-shell using too much memory after some time running

Thanks. Yes 1498M of RES (RSS) is too big.

The next step is to try disabling the default Ubuntu extensions, please.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1951072

Title:
  gnome-shell using too much memory after some time running

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It is using too much memory. Tried disabling extensions, but it
  doesn't help

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 16 11:10:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-07 (1500 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-09-26 (50 days ago)

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


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

[Desktop-packages] [Bug 1820883] Re: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"]

** 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 Desktop
Packages, which is subscribed to totem 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep

Upstream has just landed a new fix for Mutter v42:

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2103

** Changed in: mutter (Ubuntu)
   Status: Invalid => Fix Committed

** Tags removed: fixed-in-40
** Tags added: fixed-in-42

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1917939

Title:
  Windows maximise underneath dock after monitor sleep

Status in Dash to dock:
  New
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Under wayland on 21.04 windows keep maximising underneath the dock. So
  I can see icons "through" the dock, when I shouldn't. In the attached
  screenshot you can see Telegram showing through the dock.

  If I switch to the application in question, unmaximise and re-
  maximise, it goes back to maximising inside the usable area of my
  desktop.

  But when I suspend and resume, then login, I'm left with windows under
  the dock again. Never seen this under xorg. I only discovered I was in
  wayland when I tried to ALT+F2, R to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 19:21:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-11 (267 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+subscriptions


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

[Desktop-packages] [Bug 1951786] Re: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated

** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1951786

Title:
  Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already
  deallocated

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  on Ubuntu 21.10
  gnome-shell 40.5-1ubuntu2

  Locking desktop and then unlocking it makes gnome-shell spit out a
  stack trace.

  v 22 02:00:49 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor 
(0x5572c2e0f8a0), has been already deallocated — impossible to access it. This 
might be caused by the>
  Nov 22 02:00:49 saturn gnome-shell[33781]: == Stack trace for context 
0x5572c18e3130 ==
  Nov 22 02:00:49 saturn gnome-shell[33781]: #0   7ffcbc579470 b   
resource:///org/gnome/gjs/modules/core/overrides/GObject.js:567 (22c5be1b1d80 @ 
25)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #1   5572c8ea2dc0 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:159 (374b9f3380 @ 
31)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #2   7ffcbc57a1d0 b   
resource:///org/gnome/shell/ui/components/__init__.js:56 (374b9d7650 @ 66)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #3   7ffcbc57a960 b   
resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d7790 @ 15)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #4   7ffcbc57b030 b   
self-hosted:225 (374b92ab50 @ 273)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #5   5572c8ea2d30 i   
resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d78d0 @ 110)
  ...skipping...
  Nov 22 02:04:21 saturn gnome-shell[33781]: #7   7ffcbc578a80 b   
resource:///org/gnome/shell/ui/sessionMode.js:200 (25da4d8e6d30 @ 284)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #8   7ffcbc579630 b   
resource:///org/gnome/shell/ui/sessionMode.js:168 (25da4d8e6e20 @ 116)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #9   7ffcbc579dc0 b   
resource:///org/gnome/shell/ui/screenShield.js:574 (25da4d8d4a60 @ 79)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #10   7ffcbc57a550 b   
resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4ab0 @ 17)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #11   7ffcbc57acd0 b   
resource:///org/gnome/shell/gdm/authPrompt.js:604 (25da4d8f24c0 @ 65)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #12   7ffcbc57b460 b   
resource:///org/gnome/shell/ui/unlockDialog.js:871 (374b9053d0 @ 40)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #13   7ffcbc57bbf0 b   
resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4b00 @ 50)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #14   7ffcbc57c380 b   
resource:///org/gnome/shell/ui/screenShield.js:116 (25da4d8dc6f0 @ 13)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #15   7ffcbc57ca50 b   
resource:///org/gnome/gjs/modules/core/_signals.js:114 (22c5be1b1330 @ 439)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #16   5572c39ba218 i   
resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (22c5be1a5b50 @ 39)
  Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor 
(0x5572c2e0f8a0), has been already deallocated — impossible to connect to any 
signal on it. This migh>
  Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Nov 22 02:04:21 saturn dbus-daemon[33727]: [session uid=1000 pid=33727] 
Activating service name='org.freedesktop.FileManager1' requested by ':1.20' 
(uid=1000 pid=33781 comm>
  Nov 22 02:04:21 saturn gnome-shell[33781]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor 
(0x5572c2e0f8a0), has been already deallocated — impossible to access it. This 
might be caused by the>
  Nov 22 02:04:21 saturn gnome-shell[33781]: g_volume_monitor_get_volumes: 
assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: == Stack trace for context 
0x5572c18e3130 ==
  Nov 22 02:04:21 saturn gnome-shell[33781]: #0   5572c39ba218 i   
resource:///org/gnome/shell/ui/components/automountManager.js:66 (374b9f3e20 @ 
30)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #1   7ffcbc57d550 b   
self-hosted:850 (374b92a650 @ 398)
  Nov 22 02:04:21 saturn NetworkManager[1054]:   [1637564661.8704] 
agent-manager:

[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"

2021-11-22 Thread Dirk Su

Previous discussion was at
https://chat.canonical.com/canonical/pl/1mgrhibwpj8ojxk89tbpztjdar. Due
to the design of ubiquity, it only use ubuntu-driver to get package list
and install package in 31ubuntu_driver_packages. But ubuntu-driver not
only install packages but also create configurations of Nvidia GPU. This
patch will copy configurations and calling prime-select to make sure it
get same result as calling "ubuntu-driver install" directly.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1943816

Title:
  "ubuntu-drivers install" needs to be used when installing nvidia-
  driver if enabling "third-party packages"

Status in OEM Priority Project:
  Confirmed
Status in subiquity:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubiquity source package in Focal:
  New
Status in ubuntu-drivers-common source package in Focal:
  New

Bug description:
  ubiquity calls
  ```
  ubuntu-drivers install $FREEONLY $NOOEM --package-list 
/run/ubuntu-drivers.autoinstall
  ```
  to generate package list during live system but "ubuntu-drivers install" not 
only install packages but also create some config files for switching nvidia 
mode (e.g. on-demand) and change the runtime config as well (e.g. modify the 
iniramfs).

  Thus, not only package list needs to be referred but also the
  configuration.

  ---

  In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to 
install package. It also skipping the nvidia-mode changing (made by 
ubuntu-drivers install).
  ```
  $ cat ubiquity/target-config/31ubuntu_driver_packages
  #!/bin/sh
  set -e

  # install all packages that "ubuntu-drivers autoinstall" installed into the
  # live system. Ubiquity calls this with --package-list 
/run/ubuntu-drivers.autoinstall

  PKGLIST=/run/ubuntu-drivers.autoinstall
  [ -e $PKGLIST ] || exit 0

  for p in `cat $PKGLIST`; do
  apt-install $p
  done
  ```

  ---

  We need to use a same approach to make sure the nvidia mode is same on
  a same system (either all handing by ubuntu-drivers install or change
  the logic to maintainer script in each package).

  ---

  [Impact]

   * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
   * Install Ubuntu with "third-party packages" enabled, will not get same
     GPU configuration by running "ubuntu-drivers install"
   * Patch make system not enable RTD3 unless it's a laptop and set default GPU 
mode to "on-demand"

  [Test Plan]

   * Create Focal iso with live-build and import ubuntu-drivers-common from 
-proposed
   * Install Ubuntu on machine, in "Updates and other software" page select 
"Install third-party software for graphics and Wi-Fi hardware and additional 
media formats"
   * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created.
   * Call "prime-select query" to make sure the default mode is "on-demand"

  [Where problems could occur]

   * With non-laptop machine use RTD3 supported GPU may use more power

  [Other Info]

   * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer
  to https://bugs.launchpad.net/oem-priority/+bug/1942788

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


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

[Desktop-packages] [Bug 1913656] Re: `gs [options] -- ` fails with "permission denied"

2021-11-22 Thread William Wilson

racb: In order to add the steps from comment #2 as a useful test case,
another bug in ocrfeeder needed to be fixed with an SRU. See
https://bugs.launchpad.net/ubuntu/+source/ocrfeeder/+bug/1890013 for
more details.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1913656

Title:
`gs [options] -- ` fails with "permission denied"

Status in ghostscript package in Ubuntu:
Fix Released
Status in ghostscript source package in Focal:
Fix Committed

Bug description:
[Impact]
* The command line syntax `gs [options] -- ` fails
to load in the input file with a "permission denied" error.
* Per the ghostscript documentation, the `--` syntax is used as follows:
"-- filename arg1 ...
Takes the next argument as a file name as usual,
but takes all remaining arguments (even if they
have the syntactic form of switches) and defines
the name ARGUMENTS in userdict (not systemdict)
as an array of those strings, before running the
file. When Ghostscript finishes executing the file,
it exits back to the shell."

[Test Plan]
-- to be performed in a desktop environment --
* Obtain a valid input file for ghostscript. The Source package
contains an `examples/` directory with plenty to choose from.
* `gs -- `
* Observe that the test failed with a "permission denied" error.
* Install the version of ghostscript from focal-proposed.
* `gs -- `
* Observe that the command succeeds and a ghostscript window.
appears with the output of the `gs` command.

In addition see comment 6 and comment 2 for two more items in the test
plan. -- ~racb

[Regression Potential]
* Since this patch affects command line processing, it is possible
that other arguments or command line syntaxes could be affected.

[Original Description]
Ghostscript 9.50 exhibits https://bugs.ghostscript.com/show_bug.cgi?id=701894
(fix the '--' and co options) which causes (eg) ocrfeeder to fail to load PDF
files: an input file specified using the "... -- filename ..." command line
syntax has no read permission in the GS interpreter.

This commit fixes it:

http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410

GS 9.52 includes the commit.

Either apply the fix from the linked commit in the Focal-Updates
version, or upgrade it to 9.52.

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

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

[Desktop-packages] [Bug 1951828] Re: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp

2021-11-22 Thread Bug Watch Updater

** Changed in: gsl (Debian)
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsl in Ubuntu.
https://bugs.launchpad.net/bugs/1951828

Title:
   libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp

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

Bug description:
  From Debian bug 993324:

  It seems that the 2.7 upload broke the ABI of libgsl25 by removing
  the gsl_linalg_QR_TR_decomp symbol. src:gsl is currently blocked from
  entering testing because of this regression in libmath-gsl-perl_0.42-1.

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


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

[Desktop-packages] [Bug 1950467] Re: [BPO] libreoffice 7.1.7 for focal

2021-11-22 Thread Dan Streetman

> I have updated the patch

thanks! and thanks for adding details to the changelog entry as well to
clarify the backport changes, and to update the vcs links.

> The new requirement to include a "~bpo" string seems a bit unfortunate

The current rules would require the version to change as:

1:7.1.7-0ubuntu0.21.04.1
to
1:7.1.7-0ubuntu0.21.04.1~bpo20.04.1

I do think that generally makes sense, even though including both the '21.04.1' 
and '20.04.1' releases might be at first confusing. Note this does follow the 
backport version convention used by Debian:
https://backports.debian.org/Contribute/#index4h3

The only possible future problem with that versioning I think is if the
full 7.1.7 version was, at some point, *fully* SRU'ed back into focal.
At that point, the SRU version would usually be a version like
1:7.1.7-0ubuntu0.20.04.1, which would actually be a lower version number
than the version in backports. However, I don't think you are planning
to do that (right?), and it's also generally not allowed to do using the
SRU process.

Other than the version number, the backport looks good to me; if you can
upload it with the proper version number, I'm happy to approve it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1950467

Title:
  [BPO] libreoffice 7.1.7 for focal

Status in libreoffice package in Ubuntu:
  Invalid
Status in libreoffice source package in Focal:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.1.7 is in its seventh (and last) bugfix release of the 7.1 
line:
   https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release

   * This source packages matches the proposed SRU for hirsute handled at
   https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1948933
 and its backport is currently provided by the LibreOffice Still PPA at
   
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages

   * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently
  released in focal.

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Scope]

   * Backport of
  https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.7-0ubuntu0.21.04.1

   * Backport target is Focal/20.04 LTS only to provide an official
  build of a more recent upstream version of LibreOffice

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_71/1460/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/2020_055401_85a70@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/2020_013227_b21ba@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/2020_015816_7e469@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/2020_002248_216a6@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20211109_232224_7b3ab@/log.gz

   * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented
  by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 27 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1951072] Re: gnome-shell using too much memory after some time running

2021-11-22 Thread Yuriy Padlyak

Here you are:

** Attachment added: "htop.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1951072/+attachment/5542686/+files/htop.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1951072

Title:
  gnome-shell using too much memory after some time running

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It is using too much memory. Tried disabling extensions, but it
  doesn't help

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 16 11:10:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-07 (1500 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-09-26 (50 days ago)

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


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

[Desktop-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

2021-11-22 Thread Angel D. Segarra

* I found out how to repro.

Ubuntu 21.10 on Wayland session
mutter 40.5-1ubuntu3~21.10.1

If I leave any gtk apps open e.g. gnome-terminal, evince, Files open,
and then open Google Chrome with the flags to enable wayland support

--enable-features=UseOzonePlatform --ozone-platform=wayland

Then any gtk app that was open outputs the following message to journal
after any UI interaction, like switching tabs, opening context menu,
etc.

gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653
drawable is not a native X11 window

evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is
not a native X11 window

This persists until each individual app is restarted.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1951878

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Ubuntu 21.10 on Wayland session
  mutter 40.5-1ubuntu3~21.10.1

  My apologies if this does not belong in mutter but because it happens
  in multiple applications, it's my best guess.

  This is a weird bug because I don't know what causes it but it happens
  consistently after normal usage which for me means several times
  leaving the laptop idle and unlocking.

  If I leave gnome-terminal and/or evince open, eventually any UI action
  like switching from multiple tabs, opening context menu etc will
  output the following to journal

  gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653
  drawable is not a native X11 window

  evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is
  not a native X11 window

  I suspect this may happen with other gtk apps as well. This persists
  until each individual app is restarted.

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


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

[Desktop-packages] [Bug 1900472] Re: [snap] Mouse pointer scaling issue

2021-11-22 Thread Rene Horn

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1900472

Title:
  [snap] Mouse pointer scaling issue

Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  Note:

  Issue originally reported in ticket #1900334, however two symptoms are
  seen, hence creating a second ticket to track each symptom separately.

  

  Original description:

  Since updating to the latest version, the mouse pointer/cursor in
  Chromium 86.0.4240.75 (snap) on Ubuntu 20.04 does not match that shown
  on the desktop (or other non-snap applications).

  The symptom looks identical to that shown on this ticket:
  https://github.com/brave/browser-laptop/issues/9772

  See this gif: https://user-
  
images.githubusercontent.com/133786/42110742-dd3a6408-7ba7-11e8-9e7a-a1a32ff3af01.gif

  

  This ticket is intended to track the pointer scaling issue shown in
  the gif above.

  It's worth noting that this issue is seen on a HiDPI machine (4k
  monitor) with 200% desktop scaling in display settings.

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


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

[Desktop-packages] [Bug 1951878] [NEW] "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

2021-11-22 Thread Angel D. Segarra

Public bug reported:

Ubuntu 21.10 on Wayland session
mutter 40.5-1ubuntu3~21.10.1

My apologies if this does not belong in mutter but because it happens in
multiple applications, it's my best guess.

This is a weird bug because I don't know what causes it but it happens
consistently after normal usage which for me means several times leaving
the laptop idle and unlocking.

If I leave gnome-terminal and/or evince open, eventually any UI action
like switching from multiple tabs, opening context menu etc will output
the following to journal

gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653
drawable is not a native X11 window

evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is
not a native X11 window

I suspect this may happen with other gtk apps as well. This persists
until each individual app is restarted.

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1951878

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Ubuntu 21.10 on Wayland session
  mutter 40.5-1ubuntu3~21.10.1

  My apologies if this does not belong in mutter but because it happens
  in multiple applications, it's my best guess.

  This is a weird bug because I don't know what causes it but it happens
  consistently after normal usage which for me means several times
  leaving the laptop idle and unlocking.

  If I leave gnome-terminal and/or evince open, eventually any UI action
  like switching from multiple tabs, opening context menu etc will
  output the following to journal

  gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653
  drawable is not a native X11 window

  evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is
  not a native X11 window

  I suspect this may happen with other gtk apps as well. This persists
  until each individual app is restarted.

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


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

[Desktop-packages] [Bug 1951879] [NEW] System freezes

2021-11-22 Thread 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 Desktop
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 hub

[Desktop-packages] [Bug 1820883] Re: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"]

2021-11-22 Thread corrado venturini

Problem not reproducible with totem 3.38.2-1ubuntu1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951731] Re: screen freezes for several seconds

2021-11-22 Thread ulrich

This seems to solve the problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1951731

Title:
  screen freezes for several seconds

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  AMD graphics
  screen freezes for several seconds until it freezes completely

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 21 13:37:32 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-05-28 (176 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1951072] Re: gnome-shell using too much memory after some time running

2021-11-22 Thread radsaq

I'm also seeing gnome-shell in impish get up in the range of 1.5-2GB of
RSS after a couple days with just the default three extensions.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1951072

Title:
  gnome-shell using too much memory after some time running

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It is using too much memory. Tried disabling extensions, but it
  doesn't help

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 16 11:10:55 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-07 (1500 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-09-26 (50 days ago)

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


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

[Desktop-packages] [Bug 1951855] [NEW] Google Chrome freezes the system

2021-11-22 Thread 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 Desktop
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:

[Desktop-packages] [Bug 1951698] Re: [upstream] under wayland items in menu bar sub-menus cannot be moved

2021-11-22 Thread Bug Watch Updater

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1658106.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2020-08-08T07:11:30+00:00 Savvich wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0

Steps to reproduce:

Tried to drag a bookmark item, but in a blink of a second it drops back
to the spot or in a folder. Everything is OK with managing bookmarks in
a separated Library window.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1951698/comments/0

On 2020-08-08T07:17:35+00:00 Release-mgmt-account-bot wrote:

[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should
belong to this component, but please revert this change in case of
error.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1951698/comments/1

On 2020-08-08T09:15:00+00:00 Stransky wrote:

Can you try nested mutter compositor if you can reproduce it there too?
Run on terminal:

$mutter --wayland --nested &
$WAYLAND_DISPLAY=wayland-1 MOZ_ENABLE_WAYLAND=1  ./firefox

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1951698/comments/2

On 2020-08-08T09:40:05+00:00 Savvich wrote:

(In reply to Martin Stránský [:stransky] from comment #2)
> Can you try nested mutter compositor if you can reproduce it there too?
> Run on terminal:
> 
> $mutter --wayland --nested &
> $WAYLAND_DISPLAY=wayland-1 MOZ_ENABLE_WAYLAND=1  ./firefox

Tried with firefox-esr --no-remote — cannot drag-and-drop at all.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1951698/comments/3

On 2020-08-08T10:00:44+00:00 Savvich wrote:

(In reply to frodgesh from comment #3)
> (In reply to Martin Stránský [:stransky] from comment #2)
> > Can you try nested mutter compositor if you can reproduce it there too?
> > Run on terminal:
> > 
> > $mutter --wayland --nested &
> > $WAYLAND_DISPLAY=wayland-1 MOZ_ENABLE_WAYLAND=1  ./firefox
> 
> Tried with firefox-esr --no-remote — cannot drag-and-drop at all.

Just figured out to use physical click on mouse touchpad. Yes, it can be
reproduced there too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1951698/comments/4

On 2020-08-10T10:00:50+00:00 Stransky wrote:

Please use latest nightly for reproduction which is 81. Firefox 68 won't
get any Wayland fixes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1951698/comments/5

On 2020-08-10T11:34:02+00:00 Savvich wrote:

(In reply to Martin Stránský [:stransky] from comment #5)
> Please use latest nightly for reproduction which is 81. Firefox 68 won't get 
> any Wayland fixes.

What was the point of testing in mutter? This bug tracker sucks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1951698/comments/6

On 2020-08-10T12:59:36+00:00 W-jan-k wrote:

Don't make it so. ;) If a bug is reproducible across different Wayland 
compositors, it's more likely a bug in Firefox, otherwise a Wayland compositor 
bug. Please download https://nightly.mozilla.org and test with Sway and Mutter, 
thank you.
Firefox 68 is just Nightly **2019**-05-20 with some additional patches, 
therefore it's too old to test with.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1951698/comments/7

On 2020-08-10T14:43:40+00:00 Savvich wrote:

(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #7)
> Don't make it so. ;) If a bug is reproducible across different Wayland 
> compositors, it's more likely a bug in Firefox, otherwise a Wayland 
> compositor bug. Please download https://nightly.mozilla.org and test with 
> Sway and Mutter, thank you.
> Firefox 68 is just Nightly **2019**-05-20 with some additional patches, 
> therefore it's too old to test with.

Sway w/ Nightly — item drops immediately. Nested mutter w/ Nightly —
does not respect a drag-and-drop action, yet animation works, with no
"bookmark" lines between items appearing. Tested with Nightly 81. Same
with 68.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1951698/comments/8

** Changed in: firefox
   Status: Unknown => New

-- 
You received this bug notification because you are a

[Desktop-packages] [Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

** Description changed:

  Similarly to bug #1895643, which was about upgrading thunderbird from 68
  to 78 in all supported Ubuntu releases, this bug is to track the update
  from thunderbird 78 to 91 in hirsute, focal and bionic.
  
  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).
  
  Thunderbird follows the Firefox ESR release cycle, and the next/current
  series is 91 (already available in impish and jammy).
+ 
+ User-facing announcement: https://discourse.ubuntu.com/t/thunderbird-
+ lts-update-78-to-91/25391.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1949605

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  In Progress
Status in thunderbird source package in Focal:
  In Progress
Status in thunderbird source package in Hirsute:
  In Progress

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

  User-facing announcement: https://discourse.ubuntu.com/t/thunderbird-
  lts-update-78-to-91/25391.

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


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

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

2021-11-22 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951583] Re: bbswitch dkms build failure with 5.15 on armhf and ppc64el

2021-11-22 Thread Andrea Righi

** Description changed:

- It looks like bbswitch is using acpi_bus_get_device() on any
- architectures, but this function is not available on armhf or ppc64el:
+ [Impact]
+ 
+ bbswitch is failing to build with the latest jammy kernel 5.15 on armhf
+ and ppc64el.
+ 
+ The build error that we get looks like the following:
  
CC [M]  /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit 
declaration of function ‘acpi_bus_get_device’; did you mean 
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of 
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
|   ^~
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of 
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
|   ^~
+ 
+ [Test case]
+ 
+ Install bbswitch-dkms.
+ 
+ [Fix]
+ 
+ It looks like bbswitch is using acpi_bus_get_device() on any
+ architectures to check for suspend events, but this function is not
+ available on armhf or ppc64el. The fix would be to avoid doing this
+ check (and using acpi_bus_get_device()) on architectures that don't have
+ this capability.
+ 
+ [Regression potential]
+ 
+ We should see potential bbswitch regressions on armhf or ppc64el if they
+ have suspend events (similar problem that is addressed on amd64 /
+ arm64).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bbswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1951583

Title:
  bbswitch dkms build failure with 5.15 on armhf and ppc64el

Status in bbswitch package in Ubuntu:
  New
Status in bbswitch source package in Jammy:
  New

Bug description:
  [Impact]

  bbswitch is failing to build with the latest jammy kernel 5.15 on
  armhf and ppc64el.

  The build error that we get looks like the following:

CC [M]  /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:271:13: error: implicit 
declaration of function ‘acpi_bus_get_device’; did you mean 
‘acpi_get_gpe_device’? [-Werror=implicit-function-declaration]
271 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_get_gpe_device
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:276:15: error: invalid use of 
undefined type ‘struct acpi_device’
276 | if (ad->power.state == ACPI_STATE_UNKNOWN) {
|   ^~
  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:278:15: error: invalid use of 
undefined type ‘struct acpi_device’
278 | ad->power.state = ACPI_STATE_D0;
|   ^~

  [Test case]

  Install bbswitch-dkms.

  [Fix]

  It looks like bbswitch is using acpi_bus_get_device() on any
  architectures to check for suspend events, but this function is not
  available on armhf or ppc64el. The fix would be to avoid doing this
  check (and using acpi_bus_get_device()) on architectures that don't
  have this capability.

  [Regression potential]

  We should see potential bbswitch regressions on armhf or ppc64el if
  they have suspend events (similar problem that is addressed on amd64 /
  arm64).

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


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

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

2021-11-22 Thread BobbitStephane

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951698] Re: under wayland items in menu bar sub-menus cannot be moved

This sounds like this upstream bug: 
https://bugzilla.mozilla.org/show_bug.cgi?id=1658106.
Can you please comment there with your version and any relevant details?

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

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1658106
   Importance: Unknown
   Status: Unknown

** Summary changed:

- under wayland items in menu bar sub-menus cannot be moved
+ [upstream] under wayland items in menu bar sub-menus cannot be moved

** Tags added: upstream

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1951698

Title:
  [upstream] under wayland items in menu bar sub-menus cannot be moved

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  New

Bug description:
  When running firefox on wayland, it appears to be impossible to move
  bookmark items in the menu bar sub menus.

  How to reproduce:

  * haver a gnome session with wayland
  * have the menu bar toolbar activated
  * have a folder in the menu bar 
  * have multiple bookmarks in that folder
  * click on the folder icon in the menu bar, when it opens, try to drag and 
drop the item to put it into another position - e.g. from the last to the first

  Expected result:

  * the bookmark item is move to the new position - this is waht happens
  when doing these steps with firefox on gnome with an xorg sessions.

  
  Actual result: the item stays where it was.

  similarly, i cannot drag and drop a new bookmark into a folder and out
  it into the position where I want to have it.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 94.0+build3-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  henning   63267 F pulseaudio
   /dev/snd/controlC1:  henning   63267 F pulseaudio
  BuildID: 20211028161635
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
  Date: Sat Nov 20 21:21:03 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:363
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-04-12 (586 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:363
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=84.0.2/20210105180113 (Out of date)
   Profile0 - LastVersion=94.0/20211028161635 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to impish on 2021-11-14 (5 days ago)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET53W (1.40 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET53W(1.40):bd08/17/2021:br1.40:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QV00CEGE
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1947314] Re: gnome-shell-portal-helper crashed with SIGABRT in _dbus_abort() from _dbus_warn_check_failed() from dbus_message_new_method_call() from socket_embed_hook() from We

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1947314

Title:
  gnome-shell-portal-helper crashed with SIGABRT in _dbus_abort() from
  _dbus_warn_check_failed() from dbus_message_new_method_call() from
  socket_embed_hook() from WebKit() from () from WebPageProxy() from ()
  from bindAccessibilityTree()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
40.5-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/25d073bff9bf96d17026a56ca803dcd409ef42b2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1951646] Re: [snap] Firefox unable to load Security Device "p11-kit-trust.so" defined in /etc/firefox/policies/policies.json

That's indeed a snap-specific problem, and a confinement issue: the
application is not allowed to see /usr/lib/x86_64-linux-gnu/pkcs11/ on
the host system, the path is remapped to
/snap/core20/current/usr/lib/x86_64-linux-gnu/pkcs11/, which doesn't
exist.

I was able to work around the problem by downloading the p11-kit-modules
package for Ubuntu 20.04
(https://launchpad.net/ubuntu/focal/amd64/p11-kit-modules), unpacking it
in /var/snap/firefox/common/, and changing the path in
/etc/firefox/policies/policies.json to point there.

Not exactly easy, but it seems to do the job without requiring changes
to firefox or the snap itself.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1951646

Title:
  [snap] Firefox unable to load Security Device "p11-kit-trust.so"
  defined in /etc/firefox/policies/policies.json

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  Ubuntu 21.10 with default Firefox (v93.0) snap install.

  Having defined a policy in /etc/firefox/policies/policies.json with the 
following:
  $ cat /etc/firefox/policies/policies.json 
  {
  "policies": {
  "Authentication": {
  "Delegated": [
  "example.com"
  ],
  "NTLM": [
  "example.com"
  ],
  "SPNEGO": [
  "example.com"
  ],
  "Locked": false
  },
  "Homepage": {
  "URL": "https://example.com;,
  "Locked": false
  },
  "Proxy": {
  "Mode": "system",
  "Passthrough": ",.example.com,
  "Locked": false
  },
  "SecurityDevices": {
  "p11-kit-trust.so for Internal certificate chain": 
"/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so"
  }
  }
  }

  I got an error when looking over about:policies:
  "Unable to load security device p11-kit-trust.so"
  However, all other policies are active and applied correctly (meaning that 
snap firefox can load /etc/firefox/policies/policies.json file).

  After enabling debug for policies I get the following error:
  Policies.jsm: 
  Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure 
code: 0x80004005 (NS_ERROR_FAILURE) [nsIPKCS11ModuleDB.addModule]", result: 
2147500037, filename: "resource:///modules/policies/Policies.jsm", lineNumber: 
1995, columnNumber: 0, data: null, stack: 
"onProfileAfterChange@resource:///modules/policies/Policies.jsm:1995:20\n_runPoliciesCallbacks@resource://gre/modules/EnterprisePoliciesParent.jsm:238:9\nBG_observe@resource://gre/modules/EnterprisePoliciesParent.jsm:291:14\n",
 location: XPCWrappedNative_NoHelper }
  Policies.jsm:1998

  
  I tried to reproduce with the firefox.deb package without success, so the 
problem might be around snap.

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


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

[Desktop-packages] [Bug 1951786] Re: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated

2021-11-22 Thread Angel D. Segarra

Can confirm, does not happen with dock disabled. Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1951786

Title:
  Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already
  deallocated

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  on Ubuntu 21.10
  gnome-shell 40.5-1ubuntu2

  Locking desktop and then unlocking it makes gnome-shell spit out a
  stack trace.

  v 22 02:00:49 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor 
(0x5572c2e0f8a0), has been already deallocated — impossible to access it. This 
might be caused by the>
  Nov 22 02:00:49 saturn gnome-shell[33781]: == Stack trace for context 
0x5572c18e3130 ==
  Nov 22 02:00:49 saturn gnome-shell[33781]: #0   7ffcbc579470 b   
resource:///org/gnome/gjs/modules/core/overrides/GObject.js:567 (22c5be1b1d80 @ 
25)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #1   5572c8ea2dc0 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:159 (374b9f3380 @ 
31)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #2   7ffcbc57a1d0 b   
resource:///org/gnome/shell/ui/components/__init__.js:56 (374b9d7650 @ 66)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #3   7ffcbc57a960 b   
resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d7790 @ 15)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #4   7ffcbc57b030 b   
self-hosted:225 (374b92ab50 @ 273)
  Nov 22 02:00:49 saturn gnome-shell[33781]: #5   5572c8ea2d30 i   
resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d78d0 @ 110)
  ...skipping...
  Nov 22 02:04:21 saturn gnome-shell[33781]: #7   7ffcbc578a80 b   
resource:///org/gnome/shell/ui/sessionMode.js:200 (25da4d8e6d30 @ 284)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #8   7ffcbc579630 b   
resource:///org/gnome/shell/ui/sessionMode.js:168 (25da4d8e6e20 @ 116)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #9   7ffcbc579dc0 b   
resource:///org/gnome/shell/ui/screenShield.js:574 (25da4d8d4a60 @ 79)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #10   7ffcbc57a550 b   
resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4ab0 @ 17)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #11   7ffcbc57acd0 b   
resource:///org/gnome/shell/gdm/authPrompt.js:604 (25da4d8f24c0 @ 65)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #12   7ffcbc57b460 b   
resource:///org/gnome/shell/ui/unlockDialog.js:871 (374b9053d0 @ 40)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #13   7ffcbc57bbf0 b   
resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4b00 @ 50)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #14   7ffcbc57c380 b   
resource:///org/gnome/shell/ui/screenShield.js:116 (25da4d8dc6f0 @ 13)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #15   7ffcbc57ca50 b   
resource:///org/gnome/gjs/modules/core/_signals.js:114 (22c5be1b1330 @ 439)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #16   5572c39ba218 i   
resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (22c5be1a5b50 @ 39)
  Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor 
(0x5572c2e0f8a0), has been already deallocated — impossible to connect to any 
signal on it. This migh>
  Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Nov 22 02:04:21 saturn dbus-daemon[33727]: [session uid=1000 pid=33727] 
Activating service name='org.freedesktop.FileManager1' requested by ':1.20' 
(uid=1000 pid=33781 comm>
  Nov 22 02:04:21 saturn gnome-shell[33781]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor 
(0x5572c2e0f8a0), has been already deallocated — impossible to access it. This 
might be caused by the>
  Nov 22 02:04:21 saturn gnome-shell[33781]: g_volume_monitor_get_volumes: 
assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed
  Nov 22 02:04:21 saturn gnome-shell[33781]: == Stack trace for context 
0x5572c18e3130 ==
  Nov 22 02:04:21 saturn gnome-shell[33781]: #0   5572c39ba218 i   
resource:///org/gnome/shell/ui/components/automountManager.js:66 (374b9f3e20 @ 
30)
  Nov 22 02:04:21 saturn gnome-shell[33781]: #1   7ffcbc57d550 b   
self-hosted:850 (374b92a650 @ 398)
  Nov 22 02:04:21 saturn NetworkManager[1054]:   [1637564661.8704] 
agent-manager: 
agent[70e63220a742bb64,:1.631/org.gnome.Shell.NetworkAgent/1000]: agent 
registered
  Nov 22

[Desktop-packages] [Bug 344257]

2021-11-22 Thread Qa-admin-q

Dear Christopher M. Penalver,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/344257

Title:
[upstream] Impress truncates display of slide notes

Status in LibreOffice:
Confirmed
Status in OpenOffice:
Confirmed
Status in libreoffice package in Ubuntu:
Confirmed
Status in openoffice.org package in Ubuntu:
Won't Fix

Bug description:
1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

2) apt-cache policy libreoffice-impress
libreoffice-impress:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
*** 1:3.3.2-1ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386
Packages
100 /var/lib/dpkg/status
1:3.3.2-1ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

3) What is expected to happen in LibreOffice Impress via the Terminal:

cd ~/Desktop && wget

https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/344257/+attachment/497929/+files/Review.ppt
&& loimpress -nologo Review.ppt

on slide 6 click the Notes tab and all the notes are able to be
scrolled down to.

4) What happen instead is a text box is created whose boundaries are
farther down then one is allowed to scroll down to. Hence, one cannot
see all the available note text.

WORKAROUND: Highlight the text and resize to 10 so all text is visible.
WORKAROUND: Make sure extraneous spaces after text are removed before
exporting via PowerPoint.

Original Report Comments: The slide has been uploaded with the
permission of Professor Sriram Mohan for use in resolving this ticket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/344257/+subscriptions

[Desktop-packages] [Bug 1951646] Re: [snap] Firefox unable to load Security Device "p11-kit-trust.so" defined in /etc/firefox/policies/policies.json

** Tags added: snap

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1951646

Title:
  [snap] Firefox unable to load Security Device "p11-kit-trust.so"
  defined in /etc/firefox/policies/policies.json

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  Ubuntu 21.10 with default Firefox (v93.0) snap install.

  Having defined a policy in /etc/firefox/policies/policies.json with the 
following:
  $ cat /etc/firefox/policies/policies.json 
  {
  "policies": {
  "Authentication": {
  "Delegated": [
  "example.com"
  ],
  "NTLM": [
  "example.com"
  ],
  "SPNEGO": [
  "example.com"
  ],
  "Locked": false
  },
  "Homepage": {
  "URL": "https://example.com;,
  "Locked": false
  },
  "Proxy": {
  "Mode": "system",
  "Passthrough": ",.example.com,
  "Locked": false
  },
  "SecurityDevices": {
  "p11-kit-trust.so for Internal certificate chain": 
"/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so"
  }
  }
  }

  I got an error when looking over about:policies:
  "Unable to load security device p11-kit-trust.so"
  However, all other policies are active and applied correctly (meaning that 
snap firefox can load /etc/firefox/policies/policies.json file).

  After enabling debug for policies I get the following error:
  Policies.jsm: 
  Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure 
code: 0x80004005 (NS_ERROR_FAILURE) [nsIPKCS11ModuleDB.addModule]", result: 
2147500037, filename: "resource:///modules/policies/Policies.jsm", lineNumber: 
1995, columnNumber: 0, data: null, stack: 
"onProfileAfterChange@resource:///modules/policies/Policies.jsm:1995:20\n_runPoliciesCallbacks@resource://gre/modules/EnterprisePoliciesParent.jsm:238:9\nBG_observe@resource://gre/modules/EnterprisePoliciesParent.jsm:291:14\n",
 location: XPCWrappedNative_NoHelper }
  Policies.jsm:1998

  
  I tried to reproduce with the firefox.deb package without success, so the 
problem might be around snap.

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


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

[Desktop-packages] [Bug 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird

Thanks Gordon!

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1742202
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Drop-down Calendar menus unreadable in Thunderbird
+ [upstream] Drop-down Calendar menus unreadable in Thunderbird

** Tags added: upstream

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1950912

Title:
  [upstream] Drop-down Calendar menus unreadable in Thunderbird

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  New

Bug description:
  I'm using Thunderbird 91.2.1 in Impish with the Dark Theme.

  The drop-down menus for editing Calendar events (such as options for
  Repeat: and Reminder:) have light text on a light background, and are
  hence unreadable.

  This only started with the move to Impish.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gml44103277 F pulseaudio
  BuildID: 20211020014537
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Nov 14 18:03:28 2021
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-08-13 (458 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp64s0 scope link metric 1000
   192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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


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

[Desktop-packages] [Bug 1942799] Re: Exiv2 creates out of range exception with XMP data

2021-11-22 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable

2021-11-22 Thread 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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1951625] Re: thunderbird does not restart after minimizing (red dot left of icon)

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

** This bug has been marked a duplicate of bug 1932328
   Thunderbird under Wayland does not correctly close (or manage) windows

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1951625

Title:
  thunderbird does not restart after minimizing (red dot left of icon)

Status in thunderbird package in Ubuntu:
  New

Bug description:
  After interrupting a Thunderbird session by minimizing (using "-" in
  the top right corner) I can't reopen the minimized Thunderbird window
  as all other program icons do (and Thunderbird also did until about
  half a year ago!) I can not say exactly if an update caused this
  defect. Maybe Ubuntu 21.04 which I installed in April 21. Ubuntu 21.10
  update did not eliminate this. Kernel updates either (now running
  kernel 5.14.15.)

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


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

[Desktop-packages] [Bug 1951823] Re: Thunderbird mail sending window behaves incorrectly

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

** This bug has been marked a duplicate of bug 1932328
   Thunderbird under Wayland does not correctly close (or manage) windows

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1951823

Title:
  Thunderbird mail sending window behaves incorrectly

Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I open the mail sending window in Thunderbird (Ubuntu 21.10),
  send the mail, and close the sending window the dot next to the
  Thunderbird icon is not deleted. So there are two dots but only one
  Thunderbird window. When I close Thunderbird after this the dot next
  to the icon remains and I'm unable to launch Thunderbird again by
  clicking the icon.

  Ubuntu release: 21.10
  Package version (thunderbird): 1:91.3.1+build1-0ubuntu0.21.10.1

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


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

[Desktop-packages] [Bug 1920836] Re: Show Extended Security Maintenence status

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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page

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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines

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

[Desktop-packages] [Bug 1951830] [NEW] Low Disk Space is too late

2021-11-22 Thread Tero Gusto

Public bug reported:

With today's bandwidth, downloading 1 GB doesn't take long, so you could
end up running out of space only seconds after the "Low Disk Space"
warning pops up, since the thresholds are pretty tight, with less than
95% and less than 1 GB.

/org/gnome/settings-daemon/plugins/housekeeping/free-percent-notify
95%

/org/gnome/settings-daemon/plugins/housekeeping/free-size-gb-no-notify
1 GB

Suggested solution:

1. Change these values to 85% and 10 GB
2. Make them available through the GUI under "Notifications", and add "Change 
thresholds under Settings > Notifications" under the "Low Disk Space" warning 
message window

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1951830

Title:
  Low Disk Space is too late

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  With today's bandwidth, downloading 1 GB doesn't take long, so you
  could end up running out of space only seconds after the "Low Disk
  Space" warning pops up, since the thresholds are pretty tight, with
  less than 95% and less than 1 GB.

  /org/gnome/settings-daemon/plugins/housekeeping/free-percent-notify
  95%

  /org/gnome/settings-daemon/plugins/housekeeping/free-size-gb-no-notify
  1 GB

  Suggested solution:

  1. Change these values to 85% and 10 GB
  2. Make them available through the GUI under "Notifications", and add "Change 
thresholds under Settings > Notifications" under the "Low Disk Space" warning 
message window

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


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

[Desktop-packages] [Bug 1951828] [NEW] libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp

2021-11-22 Thread Graham Inggs

Public bug reported:

>From Debian bug 993324:

It seems that the 2.7 upload broke the ABI of libgsl25 by removing
the gsl_linalg_QR_TR_decomp symbol. src:gsl is currently blocked from
entering testing because of this regression in libmath-gsl-perl_0.42-1.

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

** Affects: gsl (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: update-excuse

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

** Also affects: gsl (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993324
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsl in Ubuntu.
https://bugs.launchpad.net/bugs/1951828

Title:
   libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp

Status in gsl package in Ubuntu:
  New
Status in gsl package in Debian:
  Unknown

Bug description:
  From Debian bug 993324:

  It seems that the 2.7 upload broke the ABI of libgsl25 by removing
  the gsl_linalg_QR_TR_decomp symbol. src:gsl is currently blocked from
  entering testing because of this regression in libmath-gsl-perl_0.42-1.

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


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

[Desktop-packages] [Bug 1951823] [NEW] Thunderbird mail sending window behaves incorrectly

2021-11-22 Thread Tommi Höynälänmaa

Public bug reported:

When I open the mail sending window in Thunderbird (Ubuntu 21.10), send
the mail, and close the sending window the dot next to the Thunderbird
icon is not deleted. So there are two dots but only one Thunderbird
window. When I close Thunderbird after this the dot next to the icon
remains and I'm unable to launch Thunderbird again by clicking the icon.

Ubuntu release: 21.10
Package version (thunderbird): 1:91.3.1+build1-0ubuntu0.21.10.1

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1951823

Title:
  Thunderbird mail sending window behaves incorrectly

Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I open the mail sending window in Thunderbird (Ubuntu 21.10),
  send the mail, and close the sending window the dot next to the
  Thunderbird icon is not deleted. So there are two dots but only one
  Thunderbird window. When I close Thunderbird after this the dot next
  to the icon remains and I'm unable to launch Thunderbird again by
  clicking the icon.

  Ubuntu release: 21.10
  Package version (thunderbird): 1:91.3.1+build1-0ubuntu0.21.10.1

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


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

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

I can confirm the bug still exists with mutter 40.5-1ubuntu3 and
thunderbird 1:91.3.2+build1-0ubuntu1, as tested in a fully up-to-date
jammy VM.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1932328

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Unknown
Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

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


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

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows