date:20210608

** Summary changed:

- Screen brightness of HP laptop is not saved after restart
+ [HP ENVY Laptop 15-ep0xxx] Screen brightness is not saved after restart

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

** Tags added: nvidia

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

Title:
  [HP ENVY Laptop 15-ep0xxx] Screen brightness is not saved after
  restart

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

Bug description:
  When the computer is turned on, screen brightness is always 100%
  instead of the last set brightness. The computer is HP Envy 15 laptop.
  The Ubuntu version is 20.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-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  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  9 08:13:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:878e]
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f12] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:878e]
  InstallationDate: Installed on 2021-06-05 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP ENVY Laptop 15-ep0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2020
  dmi.bios.release: 15.5
  dmi.bios.vendor: AMI
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 878E
  dmi.board.vendor: HP
  dmi.board.version: 18.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 18.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.05:bd12/29/2020:br15.5:efr18.32:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP ENVY
  dmi.product.name: HP ENVY Laptop 15-ep0xxx
  dmi.product.sku: 16P91PA#AR6
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/+source/gnome-settings-daemon/+bug/1931318/+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 1931318] Re: Screen brightness of HP laptop is not saved after restart

2021-06-08 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => xorg (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/1931318

Title:
  Screen brightness of HP laptop is not saved after restart

Status in xorg package in Ubuntu:
  New

Bug description:
  When the computer is turned on, screen brightness is always 100%
  instead of the last set brightness. The computer is HP Envy 15 laptop.
  The Ubuntu version is 20.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-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  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  9 08:13:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:878e]
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f12] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:878e]
  InstallationDate: Installed on 2021-06-05 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP ENVY Laptop 15-ep0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2020
  dmi.bios.release: 15.5
  dmi.bios.vendor: AMI
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 878E
  dmi.board.vendor: HP
  dmi.board.version: 18.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 18.32
  dmi.modalias: 
dmi:bvnAMI:bvrF.05:bd12/29/2020:br15.5:efr18.32:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP ENVY
  dmi.product.name: HP ENVY Laptop 15-ep0xxx
  dmi.product.sku: 16P91PA#AR6
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/+source/xorg/+bug/1931318/+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 1931318] [NEW] Screen brightness of HP laptop is not saved after restart

You have been subscribed to a public bug:

When the computer is turned on, screen brightness is always 100% instead
of the last set brightness. The computer is HP Envy 15 laptop. The
Ubuntu version is 20.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-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  460.80  Fri May  7 06:55:54 
UTC 2021
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun  9 08:13:44 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company Device [103c:878e]
 NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f12] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:878e]
InstallationDate: Installed on 2021-06-05 (3 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: HP HP ENVY Laptop 15-ep0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/29/2020
dmi.bios.release: 15.5
dmi.bios.vendor: AMI
dmi.bios.version: F.05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 878E
dmi.board.vendor: HP
dmi.board.version: 18.32
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 18.32
dmi.modalias: 
dmi:bvnAMI:bvrF.05:bd12/29/2020:br15.5:efr18.32:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.32:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP ENVY
dmi.product.name: HP ENVY Laptop 15-ep0xxx
dmi.product.sku: 16P91PA#AR6
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 ubuntu
-- 
Screen brightness of HP laptop is not saved after restart
https://bugs.launchpad.net/bugs/1931318
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

-- 
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 1834967] Re: Windows in Activities might be partially off screen

Anand, please open a new bug by running:

  ubuntu-bug gnome-shell-extension-ubuntu-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/1834967

Title:
  Windows in Activities might be partially off screen

Status in ubuntu-dock:
  New
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  In Progress
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-dock/+bug/1834967/+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 1930700] Re: Firefox 89 won't load pages due to many fonts

2021-06-08 Thread Kaneŝina Rinna

Setting the Firefox preference `gfx.e10s.font-list.shared` to `false`
works around this bug for me.

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

Title:
  Firefox 89 won't load pages due to many fonts

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Upgraded Firefox to 89 and it shows a crash tab every time because I
  have 22000+ fonts. In safe-mode it works, but refreshed firefox still
  has the bug.

  When starting firefox from the terminal it shows messages like:

  [Parent 42669, Main Thread] WARNING: Too many file descriptors for one
  message!: file /build/firefox-
  
Sx7Sor/firefox-89.0+build2/ipc/chromium/src/chrome/common/ipc_message_utils.h:414

  This only happens since Firefox 89 and not in 88.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 89.0+build2-0ubuntu0.21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  shemgp 5850 F pulseaudio
   /dev/snd/controlC0:  shemgp 5850 F pulseaudio
   /dev/snd/controlC1:  shemgp 5850 F pulseaudio
  BuildID: 20210527174632
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Jun  3 19:36:30 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-09-28 (2074 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:355
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=89.0/20210527174632
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to hirsute on 2021-02-16 (106 days ago)
  dmi.bios.date: 09/25/2019
  dmi.bios.release: 2.75
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB5WW (2.75 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB5WW(2.75):bd09/25/2019:br2.75:efr1.15:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.sku: LENOVO_MT_3436
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/+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 1903936] Re: Update to 1.58

2021-06-08 Thread Chris Halse Rogers

Hello Robert, or anyone else affected,

Accepted snapd-glib into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/snapd-
glib/1.58-0ubuntu0.18.04.0 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

Title:
  Update to 1.58

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Focal:
  Fix Released
Status in snapd-glib source package in Groovy:
  Fix Released
Status in snapd-glib source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  A newer snapd-glib is available that adds support for new features in snapd. 
snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates

  [Test Case]
  The reverse depends of snapd-glib should continue to function, this is 
currently:
  - gnome-software
  - gnome-initial-setup
  - pulseaudio

  [Regression Potential]
  Changes to error message carry low risk of introducing an issue if such an 
error occurred. GIR annotation changes fix a call that was previously broken, 
and is unlikely to make that any worse.
  Risks are mitigated by automatic regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1903936/+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 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage

** Also affects: bluez via
   https://github.com/bluez/bluez/issues/70
   Importance: Unknown
   Status: Unknown

** Tags added: fixed-in-5.56 fixed-upstream

** Also affects: bluez (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

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

** Tags added: rls-ff-incoming

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

Title:
  The gatt protocol has out-of-bounds read that leads to information
  leakage

Status in Bluez Utilities:
  Unknown
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  I installed the latest bluez 5.53-0ubuntu3 version using apt-get install. It 
seems that this vulnerability was silently fixed in the latest bluez5.8, and 
the cve number was not assigned.
  But this vulnerability now affects the latest ubuntu system
  This vulnerability allows an attacker to remotely obtain most of the contents 
of the heap without authentication.
  The vulnerability code is stored in cli_feat_read_cb, this function does not 
verify the offset parameter
  The vulnerability code is as follows

  gatt-database.c

  1054：static void cli_feat_read_cb(struct gatt_db_attribute *attrib,
unsigned int id, uint16_t offset,
uint8_t opcode, struct bt_att *att,
void *user_data){
  ...
  len = sizeof(state->cli_feat)-offset;
  value = len? >cli_feat[offset]: NULL;

  done:
  gatt_db_attribute_read_result(attrib, id, ecode, value, len);

  
  }
  len will become very large due to integer overflow, so that a message of mtu 
(0x90) size will be sent later
  The message content is the buffer pointed to by value, which can be most 
addresses on the heap

  poc is very simple, the core is this line of code

  memcpy([0],"\x0c\x0b\x00\x0d\x00",5);

  0xc stands for read
  \x0b\x00 represents the handle of the client feature, which can be obtained 
through the find info message, which seems to be 0b by default
  \x0d\x00 is offset0xd

  
  this vulnerability is serious
  I want to apply for a cve number, although this has been silently fixed in 
the latest version

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1926548/+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 1834967] Re: Windows in Activities might be partially off screen

2021-06-08 Thread Anand

I can interact with the windows normally, the bottom of the windows just
gets cut off sometimes.

The bottom reappears when I hover over the virtual desktops and the
right side bar expands.

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

Title:
  Windows in Activities might be partially off screen

Status in ubuntu-dock:
  New
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  In Progress
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-dock/+bug/1834967/+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 1931239] Re: System crash regulary

Thanks for the bug report. Those look like a few different unrelated
kernel crashes. This usually happens when there is a faulty RAM module
so please use these tools to do a full health check of the system
memory:

  https://www.memtest.org/

  https://www.memtest86.com/

It will take several hours so you will need to leave it running
overnight.


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

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

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

Title:
  System crash regulary

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I saw the following error in the kernel log (kern.log) directly after
  the crash occurred. I was watching my system with a tail -f kern.log
  on a remote shell.

  ---

  Jun  8 11:29:56 workstation kernel: [49956.666945] general protection fault, 
probably for non-canonical address 0xe365a4770fa8af10:  [#1] SMP NOPTI
  Jun  8 11:29:56 workstation kernel: [49956.666958] CPU: 8 PID: 706155 Comm: 
git Tainted: G  IOE 5.11.0-18-generic #19-Ubuntu
  Jun  8 11:29:56 workstation kernel: [49956.666966] Hardware name: Dell Inc. 
Precision 5820 Tower X-Series/0X75JG, BIOS 2.2.0 04/14/2020
  Jun  8 11:29:56 workstation kernel: [49956.666969] RIP: 
0010:__kmalloc+0xb2/0x250
  Jun  8 11:29:56 workstation kernel: [49956.666983] Code: 83 72 63 49 8b 00 49 
83 78 10 00 48 89 45 c0 0f 84 85 01 00 00 48 85 c0 0f 84 7c 01 00 00 41 8b 4c 
24 28 49 8b 3c 24 48 01 c1 <48> 8b 19 48 89 ce 49 33 9c 24 b8 00 00 00 48 8d 4a 
01 48 0f ce 48
  Jun  8 11:29:56 workstation kernel: [49956.666989] RSP: :ae48650b7878 
EFLAGS: 00010282
  Jun  8 11:29:56 workstation kernel: [49956.666996] RAX: e365a4770fa8aee0 RBX: 
 RCX: e365a4770fa8af10
  Jun  8 11:29:56 workstation kernel: [49956.667000] RDX: 00044185 RSI: 
0d40 RDI: 000310c0
  Jun  8 11:29:56 workstation kernel: [49956.667004] RBP: ae48650b78c0 R08: 
9f9c9fa310c0 R09: 0001
  Jun  8 11:29:56 workstation kernel: [49956.667008] R10: 0001 R11: 
 R12: 9f8d40043a00
  Jun  8 11:29:56 workstation kernel: [49956.667012] R13: 0060 R14: 
9f8d40043a00 R15: 0d40
  Jun  8 11:29:56 workstation kernel: [49956.667016] FS:  
7f2038755f80() GS:9f9c9fa0() knlGS:
  Jun  8 11:29:56 workstation kernel: [49956.667021] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jun  8 11:29:56 workstation kernel: [49956.667024] CR2: 7f2038a1c000 CR3: 
0002ac41e004 CR4: 003726e0
  Jun  8 11:29:56 workstation kernel: [49956.667029] DR0:  DR1: 
 DR2: 
  Jun  8 11:29:56 workstation kernel: [49956.667032] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 11:29:56 workstation kernel: [49956.667036] Call Trace:
  Jun  8 11:29:56 workstation kernel: [49956.667039]  ? 
ext4_find_extent+0x381/0x450
  Jun  8 11:29:56 workstation kernel: [49956.667051]  
ext4_find_extent+0x381/0x450
  Jun  8 11:29:56 workstation kernel: [49956.667058]  
ext4_ext_map_blocks+0x72/0x980
  Jun  8 11:29:56 workstation kernel: [49956.667064]  ? 
find_get_entry+0xcd/0x160
  Jun  8 11:29:56 workstation kernel: [49956.667073]  ? 
find_get_entry+0xcd/0x160
  Jun  8 11:29:56 workstation kernel: [49956.667080]  ? 
ext4_es_lookup_extent+0x164/0x210
  Jun  8 11:29:56 workstation kernel: [49956.667087]  
ext4_map_blocks+0x261/0x590
  Jun  8 11:29:56 workstation kernel: [49956.667093]  ? xas_load+0x9/0x80
  Jun  8 11:29:56 workstation kernel: [49956.667103]  ? xa_load+0x61/0x90
  Jun  8 11:29:56 workstation kernel: [49956.667110]  
ext4_mpage_readpages+0x533/0xa70
  Jun  8 11:29:56 workstation kernel: [49956.667118]  ? 
__mod_lruvec_state+0x3a/0x50
  Jun  8 11:29:56 workstation kernel: [49956.667127]  ext4_readahead+0x33/0x40
  Jun  8 11:29:56 workstation kernel: [49956.667132]  read_pages+0x89/0x270
  Jun  8 11:29:56 workstation kernel: [49956.667140]  
page_cache_ra_unbounded+0x137/0x1f0
  Jun  8 11:29:56 workstation kernel: [49956.667147]  do_page_cache_ra+0x3d/0x40
  Jun  8 11:29:56 workstation kernel: [49956.667152]  
do_sync_mmap_readahead+0x10d/0x1c0
  Jun  8 11:29:56 workstation kernel: [49956.667159]  filemap_fault+0x571/0x840
  Jun  8 11:29:56 workstation kernel: [49956.667166]  ? xas_find+0x17a/0x1d0
  Jun  8 11:29:56 workstation kernel: [49956.667172]  ? 
filemap_map_pages+0x215/0x3f0
  Jun  8 11:29:56 workstation kernel: [49956.667179]  
ext4_filemap_fault+0x32/0x50
  Jun  8 11:29:56 workstation kernel: [49956.667185]  __do_fault+0x3c/0xe0
  Jun  8 11:29:56 workstation kernel: [49956.667194]  do_fault+0xc4/0x1f0
  Jun  8 11:29:56 workstation kernel: [49956.667201]  
handle_pte_fault+0x1e5/0x260
  Jun  8 11:29:56

[Desktop-packages] [Bug 1931265] Re: gthumb uses to much memory (gnome software within xfce)

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

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

Title:
  gthumb uses to much memory (gnome software within xfce)

Status in gthumb package in Ubuntu:
  New

Bug description:
  all my ram and swap get used if i open gthumb in linux lite with xfce

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.7
  ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18
  Uname: Linux 4.15.0-139-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  8 16:21:32 2021
  DisplayManager: lightdm
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-10-12 (969 days ago)
  InstallationMedia: Linux Lite 4.2 - Release amd64
  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/gthumb/+bug/1931265/+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 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

If 'ubuntu-bug' doesn't give you appropriate feedback then try this
instead:

  apport-cli YOURFILE.crash

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

Title:
  Pulseaudio 14.2 says: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if the bluez error is related, perhaps not (this is a desktop
  without Wifi/Bluetooth).

  jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 
'org.bluez': timed out (service_start_timeout=25000ms)
  jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired,>

  Intel i3-9100, C246 chipset, 32GB ram.

  Ubuntu Budgie 21.04 installed via usb boot disk.

  It gives me a popup "error occured" every time I reboot..

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asterix1749 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Jun  1 12:48:36 2021
  InstallationDate: Installed on 2021-05-11 (21 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.release: 1.6
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x
  dmi.board.name: D3644-B1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3644-B1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: OEM-FTS
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930409/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

Ubuntu 21.04 has bug 1922353 that will look like this one. Please try
the proposed fix for bug 1922353.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+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 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

Maybe next you should try gnome-shell-extension-dashtodock (turn off
Ubuntu Dock during that) and if the same bug happens there then report
it to the developers at https://github.com/micheleg/dash-to-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/1930304

Title:
  Horizontal scroll over dock causes it to crash and disappear, and a
  temporary GUI freeze

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

Bug description:
  # Steps to reproduce
  0. have a mouse with horizontal scrolling functionality (mine is a Microsoft 
Comfort Mouse 4500 with a tilting action for horizontal scroll)
  1. move mouse pointer over the dock
  2. use the mouse scroller to scroll horizontally

  # What I expect to happen
  Nothing

  # What happens
  Mouse pointer and everything on screen freezes. After a few seconds it 
unfreezes, but all the icons from the dock are missing. I have to log out and 
back in to restore the dock.

  # Other info
  Slightly similar to LP #1875106, but I'm not using imwheel.

  I am using Wayland.

  Syslog seems to always point to this one function: "The offending
  callback was get_preferred_height(), a vfunc". I'll attach the
  relevant part from one crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 20:35:37 2021
  InstallationDate: Installed on 2020-11-30 (182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+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 1930700] Re: Firefox 89 won't load pages due to many fonts

2021-06-08 Thread Kaneŝina Rinna

I am affected by this bug too, with 18290 fonts.
`Web Content` processes segfault as soon as they are spawned.

Attached is a log of all the messages when this happens.

** Attachment added: "log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/+attachment/5503322/+files/log.txt

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

Title:
  Firefox 89 won't load pages due to many fonts

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Upgraded Firefox to 89 and it shows a crash tab every time because I
  have 22000+ fonts. In safe-mode it works, but refreshed firefox still
  has the bug.

  When starting firefox from the terminal it shows messages like:

  [Parent 42669, Main Thread] WARNING: Too many file descriptors for one
  message!: file /build/firefox-
  
Sx7Sor/firefox-89.0+build2/ipc/chromium/src/chrome/common/ipc_message_utils.h:414

  This only happens since Firefox 89 and not in 88.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 89.0+build2-0ubuntu0.21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  shemgp 5850 F pulseaudio
   /dev/snd/controlC0:  shemgp 5850 F pulseaudio
   /dev/snd/controlC1:  shemgp 5850 F pulseaudio
  BuildID: 20210527174632
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Jun  3 19:36:30 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-09-28 (2074 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:355
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=89.0/20210527174632
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to hirsute on 2021-02-16 (106 days ago)
  dmi.bios.date: 09/25/2019
  dmi.bios.release: 2.75
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB5WW (2.75 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB5WW(2.75):bd09/25/2019:br2.75:efr1.15:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.sku: LENOVO_MT_3436
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/+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 1930700] Re: Firefox 89 won't load pages due to many fonts

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

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

Title:
  Firefox 89 won't load pages due to many fonts

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Upgraded Firefox to 89 and it shows a crash tab every time because I
  have 22000+ fonts. In safe-mode it works, but refreshed firefox still
  has the bug.

  When starting firefox from the terminal it shows messages like:

  [Parent 42669, Main Thread] WARNING: Too many file descriptors for one
  message!: file /build/firefox-
  
Sx7Sor/firefox-89.0+build2/ipc/chromium/src/chrome/common/ipc_message_utils.h:414

  This only happens since Firefox 89 and not in 88.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: firefox 89.0+build2-0ubuntu0.21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  shemgp 5850 F pulseaudio
   /dev/snd/controlC0:  shemgp 5850 F pulseaudio
   /dev/snd/controlC1:  shemgp 5850 F pulseaudio
  BuildID: 20210527174632
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Jun  3 19:36:30 2021
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-09-28 (2074 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:355
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=89.0/20210527174632
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to hirsute on 2021-02-16 (106 days ago)
  dmi.bios.date: 09/25/2019
  dmi.bios.release: 2.75
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB5WW (2.75 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB5WW(2.75):bd09/25/2019:br2.75:efr1.15:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.sku: LENOVO_MT_3436
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930700/+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 1930887] Re: [snap] Thunderbird 78.11 does not play new email sound

2021-06-08 Thread Adolfo Jayme

** Tags added: snap

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  Fix Committed

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1865838] Re: no error displayed on failed fingerprint authentication

This bug was fixed in the package gnome-shell - 3.38.3-2ubuntu0.20.10.2

---
gnome-shell (3.38.3-2ubuntu0.20.10.2) groovy; urgency=medium

  * d/p/gdm-Don-t-try-to-retry-authenticating-when-the-service-is.patch:
- gdm: Don't try to retry authenticating when the service is unavailable
  (Related to lp:1915570, regression in 3.38.3-2ubuntu0.20.10.1)

gnome-shell (3.38.3-2ubuntu0.20.10.1) groovy; urgency=medium

  * Merge with debian, containing new upstream release (LP: #1915089)
  * debian/patches: Correctly handle login cancellation and failures.
Ensure the GDM workers are terminated before restarting a new auth
request, allowing fingerprint authentication to be restarted.
(LP: #1915066)
  * debian/patches: Show errors on fingerprint failures and limit retries.
(LP: #1865838)

gnome-shell (3.38.3-2) unstable; urgency=medium

  * Team upload
  * d/patches: Update to 3.38.3-3-ge3dc4401d from gnome-3-38 branch
- Fix opening Extensions app from notification
- Fix workspace layout in right-to-left locales
- Don't break window focusing if trying to take an area screenshot while
  an application such as a game has an X11 grab (LP: #1910235)

gnome-shell (3.38.3-1) unstable; urgency=medium

  * Team upload
  * d/watch: Only watch for 3.38.x versions
  * New upstream release

 -- Marco Trevisan (Treviño)   Tue, 16 Feb 2021
05:23:21 +0100

** Changed in: gnome-shell (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  no error displayed on failed fingerprint authentication

Status in gdm:
  New
Status in OEM Priority Project:
  New
Status in fprintd package in Ubuntu:
  Triaged
Status in gdm package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in fprintd source package in Focal:
  Triaged
Status in gdm source package in Focal:
  New
Status in gnome-shell source package in Focal:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  No fingerprint errors are exposed on fingerprint login failures.

  from journalctl, gdm-fingerprint shows error there after retried 5
  times of fingerprint login failed, so I open this issue here.

  [ Test case ]

  1. enroll fingerprint for your right index finger.
  2. logout
  3. login and try login by incorrect finger e.g. middle finger
  4. Each time the wrong finger is used an error is shown
  5. After 3 times retries, an authentication error is shown, suggesting
     to use another method.

  [ Regression potential]

  Wrong errors are shown during both fingerprint auth and other kinds of 
authentications.
  Password failures aren't properly exposed. Verification can't restart on 
error.

  Password authentication doesn't work anymore for users with no
  enrolled prints (as per LP: #1915570)

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 15:32:00 2020
  InstallationDate: Installed on 2020-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200301)SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865838/+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 1910235] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  The mouse stops working after trying to take an area screenshot in
  some apps on Xorg

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  Mouse stops working after taking an area screenshot

  [ Test case ]

  1. Open Chromium browser.
  2. Go to the page with the form in which there is a standard browser 
drop-down menu (form select)
  3. Open it
  4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen
  5. Try to switch between applications using the panel and check the operation 
of the mousein other applications besides browser (in my case Slack)

  [ Regression potential ]

  Grab events don't happen or pointer isn't ungrabbed when required.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-26 (71 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1910235/+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 1915089] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update to 3.38.3 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.3

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  Ideally the verification should include checking those extensions before and 
after the update to ensure the SRU isn't creating regressions
  https://launchpadlibrarian.net/511426552/gse

  [ Regression potential ]

  Icon grid behavior has some changes reverted which may lead to slight 
difference in look.
  Workspace switch fixes have been included, so workspace behavior should be 
checked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915089/+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 1910235] Re: The mouse stops working after trying to take an area screenshot in some apps on Xorg

This bug was fixed in the package gnome-shell - 3.38.3-2ubuntu0.20.10.2

---
gnome-shell (3.38.3-2ubuntu0.20.10.2) groovy; urgency=medium

  * d/p/gdm-Don-t-try-to-retry-authenticating-when-the-service-is.patch:
- gdm: Don't try to retry authenticating when the service is unavailable
  (Related to lp:1915570, regression in 3.38.3-2ubuntu0.20.10.1)

gnome-shell (3.38.3-2ubuntu0.20.10.1) groovy; urgency=medium

  * Merge with debian, containing new upstream release (LP: #1915089)
  * debian/patches: Correctly handle login cancellation and failures.
Ensure the GDM workers are terminated before restarting a new auth
request, allowing fingerprint authentication to be restarted.
(LP: #1915066)
  * debian/patches: Show errors on fingerprint failures and limit retries.
(LP: #1865838)

gnome-shell (3.38.3-2) unstable; urgency=medium

  * Team upload
  * d/patches: Update to 3.38.3-3-ge3dc4401d from gnome-3-38 branch
- Fix opening Extensions app from notification
- Fix workspace layout in right-to-left locales
- Don't break window focusing if trying to take an area screenshot while
  an application such as a game has an X11 grab (LP: #1910235)

gnome-shell (3.38.3-1) unstable; urgency=medium

  * Team upload
  * d/watch: Only watch for 3.38.x versions
  * New upstream release

 -- Marco Trevisan (Treviño)   Tue, 16 Feb 2021
05:23:21 +0100

** Changed in: gnome-shell (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  The mouse stops working after trying to take an area screenshot in
  some apps on Xorg

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  Mouse stops working after taking an area screenshot

  [ Test case ]

  1. Open Chromium browser.
  2. Go to the page with the form in which there is a standard browser 
drop-down menu (form select)
  3. Open it
  4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen
  5. Try to switch between applications using the panel and check the operation 
of the mousein other applications besides browser (in my case Slack)

  [ Regression potential ]

  Grab events don't happen or pointer isn't ungrabbed when required.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-26 (71 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1910235/+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 1915066] Re: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working

This bug was fixed in the package gnome-shell - 3.38.3-2ubuntu0.20.10.2

---
gnome-shell (3.38.3-2ubuntu0.20.10.2) groovy; urgency=medium

  * d/p/gdm-Don-t-try-to-retry-authenticating-when-the-service-is.patch:
- gdm: Don't try to retry authenticating when the service is unavailable
  (Related to lp:1915570, regression in 3.38.3-2ubuntu0.20.10.1)

gnome-shell (3.38.3-2ubuntu0.20.10.1) groovy; urgency=medium

  * Merge with debian, containing new upstream release (LP: #1915089)
  * debian/patches: Correctly handle login cancellation and failures.
Ensure the GDM workers are terminated before restarting a new auth
request, allowing fingerprint authentication to be restarted.
(LP: #1915066)
  * debian/patches: Show errors on fingerprint failures and limit retries.
(LP: #1865838)

gnome-shell (3.38.3-2) unstable; urgency=medium

  * Team upload
  * d/patches: Update to 3.38.3-3-ge3dc4401d from gnome-3-38 branch
- Fix opening Extensions app from notification
- Fix workspace layout in right-to-left locales
- Don't break window focusing if trying to take an area screenshot while
  an application such as a game has an X11 grab (LP: #1910235)

gnome-shell (3.38.3-1) unstable; urgency=medium

  * Team upload
  * d/watch: Only watch for 3.38.x versions
  * New upstream release

 -- Marco Trevisan (Treviño)   Tue, 16 Feb 2021
05:23:21 +0100

** Changed in: gnome-shell (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  Authentication is cancelled (and immediately restarted) hitting Escape
  causing fingerprint to stop working and multiple stale gdm working

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released

Bug description:
  [ Test case ]

  In the user session lockscreen (gdm login screen is fine):

  - Lock the screen
  - Hit Enter
  - Hit Escape
  - Repeat

  Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing
  after unlocked) gdm workers should not be running (a part the one used
  for logging in).

  Fingerprint unlocking is particularly hit by this as the service may
  prevent further authentication to happen until the PAM module times
  out.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654

  [ Regression potential ]

  Authenticating at login screen or at unlock screen stops working after
  wrong credentials have been used once or the request has been
  cancelled via escape key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915066/+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 1915089] Re: Update to 3.38.3 and SRU it

This bug was fixed in the package gnome-shell - 3.38.3-2ubuntu0.20.10.2

---
gnome-shell (3.38.3-2ubuntu0.20.10.2) groovy; urgency=medium

  * d/p/gdm-Don-t-try-to-retry-authenticating-when-the-service-is.patch:
- gdm: Don't try to retry authenticating when the service is unavailable
  (Related to lp:1915570, regression in 3.38.3-2ubuntu0.20.10.1)

gnome-shell (3.38.3-2ubuntu0.20.10.1) groovy; urgency=medium

  * Merge with debian, containing new upstream release (LP: #1915089)
  * debian/patches: Correctly handle login cancellation and failures.
Ensure the GDM workers are terminated before restarting a new auth
request, allowing fingerprint authentication to be restarted.
(LP: #1915066)
  * debian/patches: Show errors on fingerprint failures and limit retries.
(LP: #1865838)

gnome-shell (3.38.3-2) unstable; urgency=medium

  * Team upload
  * d/patches: Update to 3.38.3-3-ge3dc4401d from gnome-3-38 branch
- Fix opening Extensions app from notification
- Fix workspace layout in right-to-left locales
- Don't break window focusing if trying to take an area screenshot while
  an application such as a game has an X11 grab (LP: #1910235)

gnome-shell (3.38.3-1) unstable; urgency=medium

  * Team upload
  * d/watch: Only watch for 3.38.x versions
  * New upstream release

 -- Marco Trevisan (Treviño)   Tue, 16 Feb 2021
05:23:21 +0100

** Changed in: gnome-shell (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  Update to 3.38.3 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.3

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  Ideally the verification should include checking those extensions before and 
after the update to ensure the SRU isn't creating regressions
  https://launchpadlibrarian.net/511426552/gse

  [ Regression potential ]

  Icon grid behavior has some changes reverted which may lead to slight 
difference in look.
  Workspace switch fixes have been included, so workspace behavior should be 
checked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915089/+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 1931312] [NEW] i386 version of libpipewire-0.3 for Ubuntu Focal 20.04

2021-06-08 Thread Fabio C. Barrionuevo

Public bug reported:


Hi, I updated the packages today and one of them was Steam.
When trying to open Steam, it is reported missing to install 32-bit version of 
libpipewire-0.3.so.0


luzfcb@fabio-pc:~ $ STEAM_RUNTIME=0 steam 
Running Steam on focal 20.04 64-bit
STEAM_RUNTIME is disabled by the user
Error: You are missing the following 32-bit libraries, and Steam may not run:
libpipewire-0.3.so.0

I did a brief search and saw that there is no 32bit version of pipewire
0.3 release.

https://packages.ubuntu.com/search?arch=i386=pipewire


luzfcb@fabio-pc:~ $ sudo apt-get install libpipewire-0.3-0:i386
[sudo] senha para luzfcb: 
Lendo listas de pacotes... Pronto
Construindo árvore de dependências   
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote libpipewire-0.3-0:i386
E: Couldn't find any package by glob 'libpipewire-0.3-0'
E: Não foi possível encontrar o pacote através da expressão regular 
'libpipewire-0.3-0'


Are there any plans to fix this and make life for the few people still
trying to play games using Linux less difficult?

Yes or no, thanks for your hard work.

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

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

Title:
  i386 version of libpipewire-0.3 for Ubuntu Focal 20.04

Status in pipewire package in Ubuntu:
  New

Bug description:
  
  Hi, I updated the packages today and one of them was Steam.
  When trying to open Steam, it is reported missing to install 32-bit version 
of libpipewire-0.3.so.0

  
  luzfcb@fabio-pc:~ $ STEAM_RUNTIME=0 steam 
  Running Steam on focal 20.04 64-bit
  STEAM_RUNTIME is disabled by the user
  Error: You are missing the following 32-bit libraries, and Steam may not run:
  libpipewire-0.3.so.0

  I did a brief search and saw that there is no 32bit version of
  pipewire 0.3 release.

  https://packages.ubuntu.com/search?arch=i386=pipewire

  
  luzfcb@fabio-pc:~ $ sudo apt-get install libpipewire-0.3-0:i386
  [sudo] senha para luzfcb: 
  Lendo listas de pacotes... Pronto
  Construindo árvore de dependências   
  Lendo informação de estado... Pronto
  E: Impossível encontrar o pacote libpipewire-0.3-0:i386
  E: Couldn't find any package by glob 'libpipewire-0.3-0'
  E: Não foi possível encontrar o pacote através da expressão regular 
'libpipewire-0.3-0'


  
  Are there any plans to fix this and make life for the few people still trying 
to play games using Linux less difficult?

  Yes or no, thanks for your hard work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1931312/+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 1929536] Please test proposed package

Hello Jean-Baptiste, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.9-0ubuntu0.20.04.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  [SRU] GDM background configurable with gsettings

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [Description]
  Customization of the greeter is a requirement from Corporate customers.

  Currently the background (plain color or image) of the greeter is hard
  coded in the style embedded in the theme. Customizing this background
  requires to extract the style sheet from gnome-shell gresource file,
  modify it manually, recompile and deploy the new gresource, and add an
  alternative to it.

  This feature adds 4 gsettings keys to make the background of the
  greeter configurable via gsettings. The default value defined the in
  the theme is used for keys that are not set.

  [Test Case]
  1. Boot a desktop session
  2. Verify that the default aubergine background is displayed in the greeter.
  3. Login as the administrator of the machine
  4. Install systemd-container
  5. Switch to the GDM user:
    $ sudo machinectl shell gdm@ /bin/bash
  6. Apply a different background with the command:
    $ gsettings set com.ubuntu.login-screen background-picture-uri 
'file:///usr/share/backgrounds/warty-final-ubuntu.png'
  7. Logout
  8. Verify that the image 'warty-final-ubuntu.png' is displayed as the 
background of the greeter.

  [Risks / Impact]
  The changeset is minimal, isolated (Only the code of the greeter is impacted 
by the change.) and can be easily reverted.
  In case of error in the code, GDM will fail to load and it will be 
immediately visible.

  [Build]
  Builds and tested successfully locally.
  Besides the updated JS is not compiled as part of build.

  [Upstream Issue]
  https://gitlab.gnome.org/GNOME/gdm/-/issues/684

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929536/+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 1929536] Please test proposed package

Hello Jean-Baptiste, or anyone else affected,

Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.9-0ubuntu0.20.04.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  [SRU] GDM background configurable with gsettings

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [Description]
  Customization of the greeter is a requirement from Corporate customers.

  Currently the background (plain color or image) of the greeter is hard
  coded in the style embedded in the theme. Customizing this background
  requires to extract the style sheet from gnome-shell gresource file,
  modify it manually, recompile and deploy the new gresource, and add an
  alternative to it.

  This feature adds 4 gsettings keys to make the background of the
  greeter configurable via gsettings. The default value defined the in
  the theme is used for keys that are not set.

  [Test Case]
  1. Boot a desktop session
  2. Verify that the default aubergine background is displayed in the greeter.
  3. Login as the administrator of the machine
  4. Install systemd-container
  5. Switch to the GDM user:
    $ sudo machinectl shell gdm@ /bin/bash
  6. Apply a different background with the command:
    $ gsettings set com.ubuntu.login-screen background-picture-uri 
'file:///usr/share/backgrounds/warty-final-ubuntu.png'
  7. Logout
  8. Verify that the image 'warty-final-ubuntu.png' is displayed as the 
background of the greeter.

  [Risks / Impact]
  The changeset is minimal, isolated (Only the code of the greeter is impacted 
by the change.) and can be easily reverted.
  In case of error in the code, GDM will fail to load and it will be 
immediately visible.

  [Build]
  Builds and tested successfully locally.
  Besides the updated JS is not compiled as part of build.

  [Upstream Issue]
  https://gitlab.gnome.org/GNOME/gdm/-/issues/684

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929536/+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 1929536] Re: [SRU] GDM background configurable with gsettings

For the record this was fixed in Hirsute with a different bug number:

gnome-shell (3.38.3-3ubuntu2) hirsute; urgency=medium

  [ Didier Roche ]
  [ Jean-Baptiste Lallement ]
  * debian/patches/ubuntu/configure_login_screen.patch:
Make GDM background configurable with gsettings (LP: #1918613)

 -- Didier Roche  Thu, 25 Mar 2021 10:44:17 +0100

** Changed in: gnome-shell (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  [SRU] GDM background configurable with gsettings

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  [Description]
  Customization of the greeter is a requirement from Corporate customers.

  Currently the background (plain color or image) of the greeter is hard
  coded in the style embedded in the theme. Customizing this background
  requires to extract the style sheet from gnome-shell gresource file,
  modify it manually, recompile and deploy the new gresource, and add an
  alternative to it.

  This feature adds 4 gsettings keys to make the background of the
  greeter configurable via gsettings. The default value defined the in
  the theme is used for keys that are not set.

  [Test Case]
  1. Boot a desktop session
  2. Verify that the default aubergine background is displayed in the greeter.
  3. Login as the administrator of the machine
  4. Install systemd-container
  5. Switch to the GDM user:
    $ sudo machinectl shell gdm@ /bin/bash
  6. Apply a different background with the command:
    $ gsettings set com.ubuntu.login-screen background-picture-uri 
'file:///usr/share/backgrounds/warty-final-ubuntu.png'
  7. Logout
  8. Verify that the image 'warty-final-ubuntu.png' is displayed as the 
background of the greeter.

  [Risks / Impact]
  The changeset is minimal, isolated (Only the code of the greeter is impacted 
by the change.) and can be easily reverted.
  In case of error in the code, GDM will fail to load and it will be 
immediately visible.

  [Build]
  Builds and tested successfully locally.
  Besides the updated JS is not compiled as part of build.

  [Upstream Issue]
  https://gitlab.gnome.org/GNOME/gdm/-/issues/684

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929536/+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 1910235] Re: The mouse stops working after trying to take an area screenshot in some apps on Xorg

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

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

Title:
  The mouse stops working after trying to take an area screenshot in
  some apps on Xorg

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  Mouse stops working after taking an area screenshot

  [ Test case ]

  1. Open Chromium browser.
  2. Go to the page with the form in which there is a standard browser 
drop-down menu (form select)
  3. Open it
  4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen
  5. Try to switch between applications using the panel and check the operation 
of the mousein other applications besides browser (in my case Slack)

  [ Regression potential ]

  Grab events don't happen or pointer isn't ungrabbed when required.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-26 (71 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1910235/+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 1888942]

2021-06-08 Thread Maxime Accadia

I found a (not very clean) workaround based on
https://github.com/SebastianSimon/firefox-selection-fix.

See https://github.com/MAccadia/firefox-selection-
fix/tree/primary_select_fix

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

Title:
  marked url in firefox by using one click isn't copied to clipboard,
  only with a triple mouse-click

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Hi, if I click in an url in firefox, the whole url ist marked, i.e.
  highlighted.

  If I now use a click on the mousewheel to paste the content of the clipboard 
into another software, I discover that the url wasn't copied into the clipboard 
- the previous content ist filled in.
  That's confusing to me.

  I would expect: If I can mark an url in Firefox with a single mouse-click, 
which looks like a marking with a triple click, then it should be copied also 
in the clipboard.
  That would be a consisting behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matthias   1453 F pulseaudio
   /dev/snd/controlC1:  matthias   1453 F pulseaudio
   /dev/snd/pcmC1D0c:   matthias   1453 F...m pulseaudio
   /dev/snd/pcmC1D0p:   matthias   1453 F...m pulseaudio
  BuildID: 20200708170202
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 25 16:44:27 2020
  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:730
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-04-24 (92 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 
600
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:730
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=74.0.1/20200403064753 (Out of date)
   Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET53W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS06G0J
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90GJVAH
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS06G0J
  dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1888942/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2021-06-08 Thread Reuben Jackson

I too have been having this issue in Ubuntu 21.04, Gnome-shell 3.38.4.

My system has a touchpad and touchscreen, the closest i have gotten to
consistently re-create it is to use the touch screen to click on the
same launcher icon multiple times.


It is quite an annoying bug as i get it 4-5 time a session, it seems a little 
beyond a 'first bug' or id have taken a shot at looking into it.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+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 1931301] [NEW] NIC unavailable after suspend to RAM

2021-06-08 Thread Sebastian Schauenburg

Public bug reported:

Upgraded to 21.04 (hirsute) and now the network card is unavailable
after suspend to RAM (sleep state S3). It worked flawlessly up until
20.10. My workaround for now is unloading and reloading the kernel
module, but that won't work for normal users, hence this report.

NIC in its unavailable state:
  2: enp4s0:  mtu 1500 qdisc mq state DOWN group default 
qlen 1000
  link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff

NIC (from lspci):
  04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet 
Controller (rev 10)

Trying to ifconfig it down/up results in:
  SIOCSIFFLAGS: No such device

journalctl shows (right after recovering from suspend):
  NetworkManager[1911]:   [1623181236.9371] manager: sleep: wake 
requested (sleeping: yes  enabled: yes)
  NetworkManager[1911]:   [1623181236.9372] device (enp4s0): state 
change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
  NetworkManager[1911]:   [1623181236.9382] manager: NetworkManager state 
is now CONNECTED_LOCAL

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu3
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Jun  8 21:59:15 2021
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-08-25 (1748 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

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

Title:
  NIC unavailable after suspend to RAM

Status in network-manager package in Ubuntu:
  New

Bug description:
  Upgraded to 21.04 (hirsute) and now the network card is unavailable
  after suspend to RAM (sleep state S3). It worked flawlessly up until
  20.10. My workaround for now is unloading and reloading the kernel
  module, but that won't work for normal users, hence this report.

  NIC in its unavailable state:
2: enp4s0:  mtu 1500 qdisc mq state DOWN group default 
qlen 1000
link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff

  NIC (from lspci):
04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet 
Controller (rev 10)

  Trying to ifconfig it down/up results in:
SIOCSIFFLAGS: No such device

  journalctl shows (right after recovering from suspend):
NetworkManager[1911]:   [1623181236.9371] manager: sleep: wake 
requested (sleeping: yes  enabled: yes)
NetworkManager[1911]:   [1623181236.9372] device (enp4s0): state 
change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
NetworkManager[1911]:   [1623181236.9382] manager: NetworkManager 
state is now CONNECTED_LOCAL

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Jun  8 21:59:15 2021
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-25 (1748 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1931301/+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 1865838] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  no error displayed on failed fingerprint authentication

Status in gdm:
  New
Status in OEM Priority Project:
  New
Status in fprintd package in Ubuntu:
  Triaged
Status in gdm package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in fprintd source package in Focal:
  Triaged
Status in gdm source package in Focal:
  New
Status in gnome-shell source package in Focal:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  No fingerprint errors are exposed on fingerprint login failures.

  from journalctl, gdm-fingerprint shows error there after retried 5
  times of fingerprint login failed, so I open this issue here.

  [ Test case ]

  1. enroll fingerprint for your right index finger.
  2. logout
  3. login and try login by incorrect finger e.g. middle finger
  4. Each time the wrong finger is used an error is shown
  5. After 3 times retries, an authentication error is shown, suggesting
     to use another method.

  [ Regression potential]

  Wrong errors are shown during both fingerprint auth and other kinds of 
authentications.
  Password failures aren't properly exposed. Verification can't restart on 
error.

  Password authentication doesn't work anymore for users with no
  enrolled prints (as per LP: #1915570)

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 15:32:00 2020
  InstallationDate: Installed on 2020-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200301)SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865838/+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 1921963] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  SRU 3.36.9

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released
Status in yaru-theme source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.9

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  Ideally the verification should include checking those extensions before and 
after the update to ensure the SRU isn't creating regressions
  https://launchpadlibrarian.net/511426552/gse

  [ Regression potential ]

  Login a11y changed and so the usage of icons for notifications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+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 1915066] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Authentication is cancelled (and immediately restarted) hitting Escape
  causing fingerprint to stop working and multiple stale gdm working

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [ Test case ]

  In the user session lockscreen (gdm login screen is fine):

  - Lock the screen
  - Hit Enter
  - Hit Escape
  - Repeat

  Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing
  after unlocked) gdm workers should not be running (a part the one used
  for logging in).

  Fingerprint unlocking is particularly hit by this as the service may
  prevent further authentication to happen until the PAM module times
  out.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654

  [ Regression potential ]

  Authenticating at login screen or at unlock screen stops working after
  wrong credentials have been used once or the request has been
  cancelled via escape key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915066/+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 1915570] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Login screen password entry not working on systems with fingerprint
  support

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  This bug didn't affect current focal, but we still prefer to test it
  to ensure we're not regressing while fixing LP: #1865838.

  This bug is for the login package. This only affects users of the
  development release and does not affect stable users. The bug in the
  password entry causes either the password to be entered only for the
  login to hang, or when attempting to enter the password, the computer
  quickly deletes any characters entered as if backspace was being held
  therefore preventing a user from being able to log in.

  [ Test case ]

  - In a system with a fingerprint reader supported by fprintd:
    Try to login in GDM using password authentication with an user that
    has NO enrolled fingerprints
  - Logging in should be possible, and so unlocking the screen

  [ Regression potential ]

  Impossible to login with authentication methods that expose them as
  unavailable.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-02-12 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.38.1-2ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Tags:  hirsute
  Uname: Linux 5.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915570/+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 1915066] Re: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working

This bug was fixed in the package gnome-shell - 3.36.9-0ubuntu0.20.04.1

---
gnome-shell (3.36.9-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1921963):
- Improve login screen accessibility
- Prefer image-data hint over app-icon in notifications
- Plugged leak
- Fixed crashes
  * debian/patches:
- Correctly handle login cancellation and failures (LP: #1915066)
- Show errors on fingerprint failures and limit retries (LP: #1865838)
- gdm: Don't try to retry authenticating when the service is unavailable
  (LP: #1915570)
- Enable to use Escape to cancel auth requests (with limits) (LP: #1921929)

 -- Marco Trevisan (Treviño)   Wed, 31 Mar 2021
00:50:16 +0200

** Changed in: gnome-shell (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Authentication is cancelled (and immediately restarted) hitting Escape
  causing fingerprint to stop working and multiple stale gdm working

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [ Test case ]

  In the user session lockscreen (gdm login screen is fine):

  - Lock the screen
  - Hit Enter
  - Hit Escape
  - Repeat

  Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing
  after unlocked) gdm workers should not be running (a part the one used
  for logging in).

  Fingerprint unlocking is particularly hit by this as the service may
  prevent further authentication to happen until the PAM module times
  out.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654

  [ Regression potential ]

  Authenticating at login screen or at unlock screen stops working after
  wrong credentials have been used once or the request has been
  cancelled via escape key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915066/+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 1915570] Re: Login screen password entry not working on systems with fingerprint support

This bug was fixed in the package gnome-shell - 3.36.9-0ubuntu0.20.04.1

---
gnome-shell (3.36.9-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1921963):
- Improve login screen accessibility
- Prefer image-data hint over app-icon in notifications
- Plugged leak
- Fixed crashes
  * debian/patches:
- Correctly handle login cancellation and failures (LP: #1915066)
- Show errors on fingerprint failures and limit retries (LP: #1865838)
- gdm: Don't try to retry authenticating when the service is unavailable
  (LP: #1915570)
- Enable to use Escape to cancel auth requests (with limits) (LP: #1921929)

 -- Marco Trevisan (Treviño)   Wed, 31 Mar 2021
00:50:16 +0200

** Changed in: gnome-shell (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Login screen password entry not working on systems with fingerprint
  support

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  This bug didn't affect current focal, but we still prefer to test it
  to ensure we're not regressing while fixing LP: #1865838.

  This bug is for the login package. This only affects users of the
  development release and does not affect stable users. The bug in the
  password entry causes either the password to be entered only for the
  login to hang, or when attempting to enter the password, the computer
  quickly deletes any characters entered as if backspace was being held
  therefore preventing a user from being able to log in.

  [ Test case ]

  - In a system with a fingerprint reader supported by fprintd:
    Try to login in GDM using password authentication with an user that
    has NO enrolled fingerprints
  - Logging in should be possible, and so unlocking the screen

  [ Regression potential ]

  Impossible to login with authentication methods that expose them as
  unavailable.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-02-12 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.38.1-2ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Tags:  hirsute
  Uname: Linux 5.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915570/+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 1865838] Re: no error displayed on failed fingerprint authentication

This bug was fixed in the package gnome-shell - 3.36.9-0ubuntu0.20.04.1

---
gnome-shell (3.36.9-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1921963):
- Improve login screen accessibility
- Prefer image-data hint over app-icon in notifications
- Plugged leak
- Fixed crashes
  * debian/patches:
- Correctly handle login cancellation and failures (LP: #1915066)
- Show errors on fingerprint failures and limit retries (LP: #1865838)
- gdm: Don't try to retry authenticating when the service is unavailable
  (LP: #1915570)
- Enable to use Escape to cancel auth requests (with limits) (LP: #1921929)

 -- Marco Trevisan (Treviño)   Wed, 31 Mar 2021
00:50:16 +0200

** Changed in: gnome-shell (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  no error displayed on failed fingerprint authentication

Status in gdm:
  New
Status in OEM Priority Project:
  New
Status in fprintd package in Ubuntu:
  Triaged
Status in gdm package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in fprintd source package in Focal:
  Triaged
Status in gdm source package in Focal:
  New
Status in gnome-shell source package in Focal:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  No fingerprint errors are exposed on fingerprint login failures.

  from journalctl, gdm-fingerprint shows error there after retried 5
  times of fingerprint login failed, so I open this issue here.

  [ Test case ]

  1. enroll fingerprint for your right index finger.
  2. logout
  3. login and try login by incorrect finger e.g. middle finger
  4. Each time the wrong finger is used an error is shown
  5. After 3 times retries, an authentication error is shown, suggesting
     to use another method.

  [ Regression potential]

  Wrong errors are shown during both fingerprint auth and other kinds of 
authentications.
  Password failures aren't properly exposed. Verification can't restart on 
error.

  Password authentication doesn't work anymore for users with no
  enrolled prints (as per LP: #1915570)

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 15:32:00 2020
  InstallationDate: Installed on 2020-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200301)SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1865838/+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 1921929] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Cancelling an ongoing verification via Escape key doesn't work

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  When an identification is in progress, we can't cancel the user
  verification via Escape key

  [ Test case ]

  - Start authenticating an user (using a wrong password may make this easier 
to trigger)
  - Hit Escape
  - Authentication is cancelled and user can put PIN / password again

  [ Regression potential ]

  Authentication fails even if it should not, user authentication may
  lead to user to see the user lists under gdm when not expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921929/+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 1921929] Re: Cancelling an ongoing verification via Escape key doesn't work

This bug was fixed in the package gnome-shell - 3.36.9-0ubuntu0.20.04.1

---
gnome-shell (3.36.9-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1921963):
- Improve login screen accessibility
- Prefer image-data hint over app-icon in notifications
- Plugged leak
- Fixed crashes
  * debian/patches:
- Correctly handle login cancellation and failures (LP: #1915066)
- Show errors on fingerprint failures and limit retries (LP: #1865838)
- gdm: Don't try to retry authenticating when the service is unavailable
  (LP: #1915570)
- Enable to use Escape to cancel auth requests (with limits) (LP: #1921929)

 -- Marco Trevisan (Treviño)   Wed, 31 Mar 2021
00:50:16 +0200

** Changed in: gnome-shell (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Cancelling an ongoing verification via Escape key doesn't work

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  When an identification is in progress, we can't cancel the user
  verification via Escape key

  [ Test case ]

  - Start authenticating an user (using a wrong password may make this easier 
to trigger)
  - Hit Escape
  - Authentication is cancelled and user can put PIN / password again

  [ Regression potential ]

  Authentication fails even if it should not, user authentication may
  lead to user to see the user lists under gdm when not expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921929/+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 1921963] Re: SRU 3.36.9

This bug was fixed in the package gnome-shell - 3.36.9-0ubuntu0.20.04.1

---
gnome-shell (3.36.9-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1921963):
- Improve login screen accessibility
- Prefer image-data hint over app-icon in notifications
- Plugged leak
- Fixed crashes
  * debian/patches:
- Correctly handle login cancellation and failures (LP: #1915066)
- Show errors on fingerprint failures and limit retries (LP: #1865838)
- gdm: Don't try to retry authenticating when the service is unavailable
  (LP: #1915570)
- Enable to use Escape to cancel auth requests (with limits) (LP: #1921929)

 -- Marco Trevisan (Treviño)   Wed, 31 Mar 2021
00:50:16 +0200

** Changed in: gnome-shell (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  SRU 3.36.9

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released
Status in yaru-theme source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.9

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  Ideally the verification should include checking those extensions before and 
after the update to ensure the SRU isn't creating regressions
  https://launchpadlibrarian.net/511426552/gse

  [ Regression potential ]

  Login a11y changed and so the usage of icons for notifications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+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 1910235] Re: The mouse stops working after trying to take an area screenshot in some apps on Xorg

2021-06-08 Thread Treviño

No hang reported with

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.38.3-2ubuntu0.20.10.2
  Candidate: 3.38.3-2ubuntu0.20.10.2
  Version table:
 *** 3.38.3-2ubuntu0.20.10.2 500
500 http://us.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 3.38.2-1ubuntu1~20.10.1 500
500 http://us.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
 3.38.1-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

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

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

Title:
  The mouse stops working after trying to take an area screenshot in
  some apps on Xorg

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  Mouse stops working after taking an area screenshot

  [ Test case ]

  1. Open Chromium browser.
  2. Go to the page with the form in which there is a standard browser 
drop-down menu (form select)
  3. Open it
  4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen
  5. Try to switch between applications using the panel and check the operation 
of the mousein other applications besides browser (in my case Slack)

  [ Regression potential ]

  Grab events don't happen or pointer isn't ungrabbed when required.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-26 (71 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1910235/+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 1915066] Re: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working

2021-06-08 Thread Treviño

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.38.3-2ubuntu0.20.10.2
  Candidate: 3.38.3-2ubuntu0.20.10.2
  Version table:
 *** 3.38.3-2ubuntu0.20.10.2 500
500 http://us.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 3.38.2-1ubuntu1~20.10.1 500
500 http://us.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
 3.38.1-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

$ ps aux |grep gdm-session-worker
root4722  0.0  0.2 324448 10188 ?Sl   12:22   0:00 
gdm-session-worker [pam/gdm-password]

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

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

Title:
  Authentication is cancelled (and immediately restarted) hitting Escape
  causing fingerprint to stop working and multiple stale gdm working

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Committed
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [ Test case ]

  In the user session lockscreen (gdm login screen is fine):

  - Lock the screen
  - Hit Enter
  - Hit Escape
  - Repeat

  Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing
  after unlocked) gdm workers should not be running (a part the one used
  for logging in).

  Fingerprint unlocking is particularly hit by this as the service may
  prevent further authentication to happen until the PAM module times
  out.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654

  [ Regression potential ]

  Authenticating at login screen or at unlock screen stops working after
  wrong credentials have been used once or the request has been
  cancelled via escape key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915066/+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 1915089] Re: Update to 3.38.3 and SRU it

2021-06-08 Thread Treviño

All works fine from my test

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.38.3-2ubuntu0.20.10.2
  Candidate: 3.38.3-2ubuntu0.20.10.2
  Version table:
 *** 3.38.3-2ubuntu0.20.10.2 500
500 http://us.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 3.38.2-1ubuntu1~20.10.1 500
500 http://us.archive.ubuntu.com/ubuntu groovy-updates/main amd64 
Packages
 3.38.1-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

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

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

Title:
  Update to 3.38.3 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.3

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  Ideally the verification should include checking those extensions before and 
after the update to ensure the SRU isn't creating regressions
  https://launchpadlibrarian.net/511426552/gse

  [ Regression potential ]

  Icon grid behavior has some changes reverted which may lead to slight 
difference in look.
  Workspace switch fixes have been included, so workspace behavior should be 
checked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915089/+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 1931300] [NEW] Nautilus mounts Google-drive while the Internet is down.

2021-06-08 Thread BertN45

Public bug reported:

This bug report is produced with a working internet of course. The problem 
occurred when my local network was still working fine, but the connection to 
the Internet was lost due to a failing Ethernet cable from my local network 
router to the ISP router.
 I mount the Google Drive at each login as follows: sh -c "rclone 
--vfs-cache-mode writes mount Google-drive: /media/Google-drive". Always it 
works fine, except with the failing cable. The Google drive has been shown 
after 25 seconds of by Nautilus, despite a completely missing connection with 
the Internet. It took Nautilus 25 seconds to display its window the first time. 
 My Google drive has according to Conky now 1 PiB :) and it is impossible to 
dismount the Google Drive, for details see the screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: nautilus 1:3.38.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun  8 15:35:16 2021
InstallationDate: Installed on 2019-11-30 (556 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: nautilus
UpgradeStatus: Upgraded to hirsute on 2021-03-24 (75 days ago)
usr_lib_nautilus:
 evince40.1-1
 file-roller   3.38.1-1
 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
 nautilus-share0.7.3-2ubuntu3

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


** Tags: amd64 apport-bug hirsute

** Attachment added: "Screenshot from 2021-06-04 04-56-54.png"
   
https://bugs.launchpad.net/bugs/1931300/+attachment/5503235/+files/Screenshot%20from%202021-06-04%2004-56-54.png

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

Title:
  Nautilus mounts Google-drive while the Internet is down.

Status in nautilus package in Ubuntu:
  New

Bug description:
  This bug report is produced with a working internet of course. The problem 
occurred when my local network was still working fine, but the connection to 
the Internet was lost due to a failing Ethernet cable from my local network 
router to the ISP router.
   I mount the Google Drive at each login as follows: sh -c "rclone 
--vfs-cache-mode writes mount Google-drive: /media/Google-drive". Always it 
works fine, except with the failing cable. The Google drive has been shown 
after 25 seconds of by Nautilus, despite a completely missing connection with 
the Internet. It took Nautilus 25 seconds to display its window the first time. 
 My Google drive has according to Conky now 1 PiB :) and it is impossible to 
dismount the Google Drive, for details see the screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  8 15:35:16 2021
  InstallationDate: Installed on 2019-11-30 (556 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-03-24 (75 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1931300/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-06-08 Thread Thiago Jung Bauermann

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1598
   https://gitlab.freedesktop.org/drm/amd/-/issues/1598

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #920
   https://gitlab.freedesktop.org/drm/amd/-/issues/920

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

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

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

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

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

2021-06-08 Thread Thiago Jung Bauermann

Thanks for your input.

Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu:
> Can you narrow down which specific firmware file causes the problem?

Ok, I will try.

Also, is it possible and/or worthwhile trying to bisect firmware versions from 
the linux-firmware repo? How coupled is the firmware with the kernel 
driver? E.g., can I try using firmware files from 1 year ago with current 
kernel and Mesa?

> We haven't been able to repro this.

One thing that’s a bit “fishy” about my machine is that it doesn’t seem to 
have a good clock:

[0.211436] TSC synchronization [CPU#0 -> CPU#1]:
[0.211436] Measured 3304683447 cycles TSC warp between CPUs, turning off 
TSC clock.
[0.211436] tsc: Marking TSC unstable due to check_tsc_sync_source failed
…
[0.252117] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0 
[0.252117] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
[0.253970] clocksource: Switched to clocksource hpet
…
[0.580451] Unstable clock detected, switching default tracing clock to 
"global"
   If you want to keep using the local clock, then add:
 "trace_clock=local"
   on the kernel command line

Could this bug be related to that?

> I think it may be related to a change in mesa.  Specifically mesa commit
> 820dec3f7c7.  For more info see
> https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

I’ll run with Mario’s build of Mesa with that patch backported.
Thanks, Mario!

> ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4866
>https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

Other upstream issues that look similar:

https://gitlab.freedesktop.org/drm/amd/-/issues/1598
https://gitlab.freedesktop.org/drm/amd/-/issues/920

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

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

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1928458] Re: inconsistent and unneeded password prompts

2021-06-08 Thread Nicolas Damgaard Larsen

I appreciate your reply.

> Are you using auto-logging?
On this machine I am using auto-login, yes.

> if you use password login and the keyring has the same secret then it's 
> automatically unlocked
As already stated, this behaviour has been observed both when the keyring has 
been unlocked and when not.

> the first software to try to use it is going to trigger the prompting
This behaviour has also been observed for applications not requesting for 
passwords.

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

Title:
  inconsistent and unneeded password prompts

Status in gnome-keyring package in Ubuntu:
  Incomplete

Bug description:
  On several occasions I have experienced that gnome-keyring prompts to be 
unlocked when I believe it should not.
  * I have Spotify installed as a .deb. When starting Spotify, on some 
occasions gnome-keyring prompts to be unlocked, on others not. This behaviour 
has been observed both when gnome-keyring has been unlocked in advance as well 
as when not. I have not added my Spotify password to gnome-keyring.
  * same behaviour as described above when starting Lutris. Did also not add 
any Lutris related passwords to gnome-keyring.
  * similar behaviour is observed with other applications where no passwords 
have been added to gnome-keyring.

  Whether or not I actually unlock the keyring, it has no functional
  impact in these cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 14 13:24:00 2021
  InstallationDate: Installed on 2020-05-09 (369 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1928458/+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 1931285] [NEW] Software Updater asking to update to 20.04 but I'm already on 20.10

2021-06-08 Thread aaa

Private bug reported:

I upgraded to 20.10 from the command line almost as soon as it came out
(like 7-8 months ago), and recently Software Updater has been asking me
to "upgrade" to 20.04, see this screen shot
https://i.imgur.com/RoeKMBj.png

I even clicked yes to upgrade and it kinda just didn't do anything, all
I saw was some generic error message twice.

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

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

Title:
  Software Updater asking to update to 20.04 but I'm already on 20.10

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  I upgraded to 20.10 from the command line almost as soon as it came
  out (like 7-8 months ago), and recently Software Updater has been
  asking me to "upgrade" to 20.04, see this screen shot
  https://i.imgur.com/RoeKMBj.png

  I even clicked yes to upgrade and it kinda just didn't do anything,
  all I saw was some generic error message twice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1931285/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-06-08 Thread Mario Limonciello

Here's a PPA build with the mesa fix Alex mentioned backported:
https://launchpad.net/~superm1/+archive/ubuntu/lp1928393

If you can follow the directions to add that PPA and upgrade to that
mesa package you can see if that indeed fixes it.

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: 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/1928393

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

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1931272] [NEW] [SRU] libreoffice 7.1.4 for hirsute

2021-06-08 Thread Rico Tzschichholz

Public bug reported:

[Impact]

 * LibreOffice 7.1.4 is in its forth bugfix release of the 7.1 line:
 https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.4_release

 * Version 7.1.3 is currently released in hirsute. For a list of fixed bugs 
compared to 7.1.3 see the list of bugs fixed in the release candidates of 7.1.4 
(that's a total of 79 bugs):
 https://wiki.documentfoundation.org/Releases/7.1.4/RC1#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/7.1.4/RC2#List_of_fixed_bugs

 * 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.

[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/1220/

  * 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-hirsute-libreoffice-libreoffice-prereleases/hirsute/amd64/libr/libreoffice/20210607_174726_685e9@/log.gz
* [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/arm64/libr/libreoffice/20210608_013339_0abc1@/log.gz
* [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/armhf/libr/libreoffice/20210607_175937_445f4@/log.gz
* [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/ppc64el/libr/libreoffice/20210607_221555_8f69a@/log.gz
* [s390x] ...

 * 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 79 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.

** Affects: libreoffice (Ubuntu)
 Importance: High
 Assignee: Rico Tzschichholz (ricotz)
 Status: In Progress

** Affects: libreoffice (Ubuntu Hirsute)
 Importance: High
 Assignee: Rico Tzschichholz (ricotz)
 Status: In Progress

** Also affects: libreoffice (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

** Changed in: libreoffice (Ubuntu Hirsute)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

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

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

Title:
  [SRU] libreoffice 7.1.4 for hirsute

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.1.4 is in its forth bugfix release of the 7.1 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.4_release

   * Version 7.1.3 is currently released in hirsute. For a list of fixed bugs 
compared to 7.1.3 see the list of bugs fixed in the release candidates of 7.1.4 
(that's a total of 79 bugs):
   https://wiki.documentfoundation.org/Releases/7.1.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.1.4/RC2#List_of_fixed_bugs

   * 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.

  [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).

[Desktop-packages] [Bug 1919977] Re: heap-buffer-overflow in old libwebp

2021-06-08 Thread Marc Deslauriers

There was an update to libwebp that fixed a bunch of security issues:

https://ubuntu.com/security/notices/USN-4971-1

Could you test again to see if the issue is resolved? Thanks!

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

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

Title:
  heap-buffer-overflow in old libwebp

Status in libwebp package in Ubuntu:
  Incomplete

Bug description:
  
  I found an overflow error when testing the security of ImageMagick on 
ubuntu20.02. The error exists in the libwebp library, and the old version is 
used in the system source. When ImageMagick calls the libwebp library to parse 
the webp file, an overflow occurs.

  system info:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  Codename: focal

  Edith by issues:https://github.com/ImageMagick/ImageMagick/issues/3403

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1919977/+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 1931265] [NEW] gthumb uses to much memory (gnome software within xfce)

2021-06-08 Thread bernard

Public bug reported:

all my ram and swap get used if i open gthumb in linux lite with xfce

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.7
ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18
Uname: Linux 4.15.0-139-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Jun  8 16:21:32 2021
DisplayManager: lightdm
GsettingsChanges:
 
InstallationDate: Installed on 2018-10-12 (969 days ago)
InstallationMedia: Linux Lite 4.2 - Release amd64
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  gthumb uses to much memory (gnome software within xfce)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  all my ram and swap get used if i open gthumb in linux lite with xfce

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.7
  ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18
  Uname: Linux 4.15.0-139-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  8 16:21:32 2021
  DisplayManager: lightdm
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-10-12 (969 days ago)
  InstallationMedia: Linux Lite 4.2 - Release amd64
  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/1931265/+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 1931264] [NEW] Random, unsolicited (no mouse or keyboard input), scrolling.

2021-06-08 Thread RodHorning

Public bug reported:

Web browsers (and I've also noticed this in the text editor) will
randomly scroll up and/or down.  This occurs without mouse movement or
keyboard input.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 89.0+build2-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
Uname: Linux 5.4.0-74-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tscs-admin  137848 F pulseaudio
BuildID: 20210527174632
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun  8 10:30:40 2021
ExecutablePath: /usr/lib/firefox/firefox
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2019-08-02 (676 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
IpRoute:
 default via 192.168.1.1 dev eno1 proto static metric 100 
 169.254.0.0/16 dev eno1 scope link metric 1000 
 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.222 metric 100
Locales: extensions.sqlite corrupt or missing
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:355
PrefSources: prefs.js
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=89.0/20210527174632 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to focal on 2020-07-25 (318 days ago)
dmi.bios.date: 07/05/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0125.2011.0705.1517
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67BL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10189-209
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0125.2011.0705.1517:bd07/05/2011:svnSeneca:pnpro270296:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-209:cvn:ct3:cvr:
dmi.product.name: pro270296
dmi.sys.vendor: Seneca

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


** Tags: amd64 apport-bug focal

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

Title:
  Random, unsolicited (no mouse or keyboard input), scrolling.

Status in firefox package in Ubuntu:
  New

Bug description:
  Web browsers (and I've also noticed this in the text editor) will
  randomly scroll up and/or down.  This occurs without mouse movement or
  keyboard input.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 89.0+build2-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
  Uname: Linux 5.4.0-74-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tscs-admin  137848 F pulseaudio
  BuildID: 20210527174632
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  8 10:30:40 2021
  ExecutablePath: /usr/lib/firefox/firefox
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-08-02 (676 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.1.1 dev eno1 proto static metric 100 
   169.254.0.0/16 dev eno1 scope link metric 1000 
   192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.222 metric 100
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:355
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=89.0/20210527174632 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-07-25 (318 days ago)
  dmi.bios.date: 07/05/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0125.2011.0705.1517
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-209
  dmi.chassis.type: 3
  dmi.modalias:

[Desktop-packages] [Bug 1930937] Re: Default dependency resolution in Focal pulls in full GNOME Desktop

2021-06-08 Thread Alberto Milone

** Changed in: screen-resolution-extra (Ubuntu)
   Status: New => Triaged

** Changed in: screen-resolution-extra (Ubuntu)
   Importance: Undecided => Medium

** Changed in: screen-resolution-extra (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Also affects: screen-resolution-extra (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: screen-resolution-extra (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: screen-resolution-extra (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: screen-resolution-extra (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: screen-resolution-extra (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: screen-resolution-extra (Ubuntu Focal)
   Status: New => Triaged

** Changed in: screen-resolution-extra (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: screen-resolution-extra (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: screen-resolution-extra (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: screen-resolution-extra (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: screen-resolution-extra (Ubuntu Groovy)
   Status: New => Triaged

** Changed in: screen-resolution-extra (Ubuntu Hirsute)
   Status: New => Triaged

** Changed in: screen-resolution-extra (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: screen-resolution-extra (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: screen-resolution-extra (Ubuntu Groovy)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: screen-resolution-extra (Ubuntu Hirsute)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  Default dependency resolution in Focal pulls in full GNOME Desktop

Status in screen-resolution-extra package in Ubuntu:
  Triaged
Status in screen-resolution-extra source package in Bionic:
  Triaged
Status in screen-resolution-extra source package in Focal:
  Triaged
Status in screen-resolution-extra source package in Groovy:
  Triaged
Status in screen-resolution-extra source package in Hirsute:
  Triaged

Bug description:
  In Bionic, screen-resolution-extra has a dependency on
  policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a
  dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent.
  As a result, when install screen-resolution-extra (e.g. as a
  dependency of nvidia-settings) on a system that doesn't already have
  GNOME or another polkit auth agent installed, the default dependency
  resolution pulls in a full GNOME desktop in Focal, while it does not
  do so under the same circumstances in Bionic. This can be worked
  around by explicitly installing policykit-1-gnome (or another package
  which provides the polkit-1-auth-agent virtual package), but it would
  be nice to not pull in GNOME by default on a system that doesn't
  already have it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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 1928360] Re: Switch to Fcitx 5 for Chinese

2021-06-08 Thread handsome_feng

> @handsome_feng: Since Kylin will ship both fcitx 4 and fcitx 5 in 21.10, I'm 
> thinking that Kylin
> would be a perfect platform for testing this input configuration. So it would 
> be good if you
> could include some testing also of fcitx 5 and be attentive to possible 
> issues in light of the
> fact that it loads the fcitx 4 im modules instead of the fcitx 5 ones.

Okay, we will test it in the near future, and if there are any problems,
we will feedback here.

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

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Snappy:
  Invalid
Status in Ubuntu Kylin:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1931234] Re: package libraptor2-0 2.0.14-1 failed to install/upgrade: sub-processo dpkg-deb --fsys-tarfile retornou estado de saída de erro 2

2021-06-08 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: fsys-tarfile-error

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

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

Title:
  package libraptor2-0 2.0.14-1 failed to install/upgrade: sub-processo
  dpkg-deb --fsys-tarfile retornou estado de saída de erro 2

Status in raptor2 package in Ubuntu:
  Invalid

Bug description:
  sempre ocorre na inicialização

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libraptor2-0 2.0.14-1
  ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-142-generic i686
  ApportVersion: 2.20.1-0ubuntu2.30
  AptOrdering:
   libraptor2-0: Install
   libraptor2-0: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Sun May 30 11:07:21 2021
  ErrorMessage: sub-processo dpkg-deb --fsys-tarfile retornou estado de saída 
de erro 2
  InstallationDate: Installed on 2021-05-10 (28 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.7
   apt  1.2.35
  SourcePackage: raptor2
  Title: package libraptor2-0 2.0.14-1 failed to install/upgrade: sub-processo 
dpkg-deb --fsys-tarfile retornou estado de saída de erro 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/raptor2/+bug/1931234/+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 1930887] Re: [snap] Thunderbird 78.11 does not play new email sound

2021-06-08 Thread Sebastien Bacher

Thanks for testing and confirming the fix!

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  Fix Committed

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object

2021-06-08 Thread Kenneth Loafman

Thanks for your patience with this!


** Changed in: duplicity
   Status: In Progress => Invalid

** Changed in: duplicity
Milestone: 0.8.20 => None

** Changed in: duplicity
 Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)

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

Title:
  Error when using S3 multipart upload - TypeError: cannot use a string
  pattern on a bytes-like object

Status in Duplicity:
  Invalid
Status in duplicity package in Ubuntu:
  New

Bug description:
  I followed the solution in
  https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I
  was running duplicity 0.8.11.1612-1 as well), but after upgrading to
  0.8.19, the problem still persists for me when trying to use S3
  multipart uploads.

  Note: This problem doesn't appear to exist in duplicity 0.7.17 running
  on python2.7, which is making me wonder if this is a python3.8 related
  issue.


  user@host:~$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  user@host:~$ apt-cache policy duplicity
  duplicity:
Installed: 0.8.19-ppa202104291804~ubuntu20.04.1
Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1
Version table:
   *** 0.8.19-ppa202104291804~ubuntu20.04.1 500
  500 
http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main 
amd64 Packages
  100 /var/lib/dpkg/status
   0.8.11.1612-1 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 
Packages

  Start duply v2.2, time is 2021-06-02 22:58:11.
  Using profile '/root/.duply/artifactory_backup'.
  Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), 
gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, 
GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(1)-release 
(x86_64-pc-linux-gnu)'.
  Checking TEMP_DIR '/tmp' is a folder and writable (OK)
  Test - En/Decryption skipped. (GPG disabled)

  --- Start running command PRE at 22:58:11.550 ---
  Skipping n/a script '/root/.duply/artifactory_backup/pre'.
  --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 ---

  --- Start running command BKP at 22:58:11.595 ---
  Using archive dir: /root/.cache/duplicity/duply_artifactory_backup
  Using backup name: duply_artifactory_backup
  GPG binary is gpg, version (2, 2, 19)
  Import of duplicity.backends.adbackend Succeeded
  Import of duplicity.backends.azurebackend Succeeded
  Import of duplicity.backends.b2backend Succeeded
  Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk'
  Import of duplicity.backends.cfbackend Succeeded
  Import of duplicity.backends.dpbxbackend Succeeded
  Import of duplicity.backends.gdocsbackend Succeeded
  Import of duplicity.backends.gdrivebackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.hubicbackend Succeeded
  Import of duplicity.backends.idrivedbackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.jottacloudbackend Succeeded
  Import of duplicity.backends.lftpbackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.mediafirebackend Succeeded
  Import of duplicity.backends.megabackend Succeeded
  Import of duplicity.backends.megav2backend Succeeded
  Import of duplicity.backends.megav3backend Succeeded
  Import of duplicity.backends.multibackend Succeeded
  Import of duplicity.backends.ncftpbackend Succeeded
  Import of duplicity.backends.onedrivebackend Succeeded
  Import of duplicity.backends.par2backend Succeeded
  Import of duplicity.backends.pcabackend Succeeded
  Import of duplicity.backends.pydrivebackend Succeeded
  Import of duplicity.backends.rclonebackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.s3_boto3_backend Succeeded
  Multiprocessing is not supported on linux, will use threads instead.
  Import of duplicity.backends.s3_boto_backend Succeeded
  Import of duplicity.backends.ssh_paramiko_backend Succeeded
  Import of duplicity.backends.ssh_pexpect_backend Succeeded
  Import of duplicity.backends.swiftbackend Succeeded
  Import of duplicity.backends.sxbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  Setting multipart boto backend process pool to 4 processes
  Reading globbing filelist /root/.duply/artifactory_backup/exclude
  Main action: inc
  Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile'
  

  duplicity 0.8.19
  Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption 
--verbosity 9 --full-if-older-than 7D --volsize 1024

[Desktop-packages] [Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

2021-06-08 Thread Christian Ehrhardt 

Also blocking isc-dhcp now, added a task

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

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

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in gdm3 package in Ubuntu:
  Incomplete
Status in glibc package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
  before now slipping into a bad mode.

  Now it seems all tests failed in boot-and-services by hanging until killed by
  VirtSubproc.Timeout of autokgtest.

  The last [1] test log has a bit more, it shows a python stack overflow
  ```
 VirtSubproc.Timeout
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f108e840740 (most recent call first):
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
  ```

  I have seen a bunch of packages including even gdm3 and glibc being blocked by
  that so I wanted to at least track down the issue until we can put it on
  someones task list to resolve.
  No one replied to my pings yet, but maybe that means someone is already
  debugging this and had enabled some debugging?

  By running the same in armhf container on arm64 VM on canonistack I've seen
  no issues. The test worked fine and had no hang/issues.

  root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
  lxc
  1
  test_profile (__main__.AppArmorTest)
  AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
  test_help (__main__.CLITest)
  --help works and succeeds ... ok
  test_invalid_option (__main__.CLITest)
  Calling with invalid option fails ... ok
  test_version (__main__.CLITest)
  --version works and succeeds ... ok
  test_cpushares (__main__.CgroupsTest)
  service with CPUShares ... ok
  test_simple (__main__.CgroupsTest)
  simple service ... ok
  test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does 
not work in containers'
  test_log_for_service (__main__.JournalTest) ... ok
  test_no_options (__main__.JournalTest) ... ok
  test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_failing (__main__.SeccompTest) ... ok
  test_0_init (__main__.ServicesTest)
  Verify that init is systemd ... ok
  test_cron (__main__.ServicesTest) ... ok
  test_dbus (__main__.ServicesTest) ... ok
  test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found'
  test_logind (__main__.ServicesTest) ... ok
  test_network_manager (__main__.ServicesTest) ... ok
  test_no_failed (__main__.ServicesTest)
  No failed units ... ok
  test_rsyslog (__main__.ServicesTest) ... ok
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'
  --
  Ran 23 tests in 5.589s
  OK (skipped=6)

  So I can not reproduce this on canonistack, but it blocks autopkgtests of
  various packages pretty reproducibly :-/

  [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1931088/+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 1930887] Re: [snap] Thunderbird 78.11 does not play new email sound

2021-06-08 Thread Francois Thirioux

I can confirm it works (TB 78.11 snap, Debian 11) with default sound.
I can select a custom sound and it works too (displayed location: 
file:///run/user/1000/[etc.]).

Great, thanks!

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  Fix Committed

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1925238] Re: [nvidia-prime] switches between xorg and wayland session

2021-06-08 Thread Alberto Milone

I think we need better detection code upstream, since the NVIDIA 470
driver will have full Wayland (and accelerated XWayland) support, and
the udev rule should take this into account.

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

Title:
  [nvidia-prime] switches between xorg and wayland session

Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Impish:
  New

Bug description:
  I have noticed this on a hirsute install from today's RC media
  (20210420) with ubuntu-drivers-common 1:0.8.9.1.

  The first boot is always xorg, and nvidia mode is selected.

  After that reboots are *usually* wayland, but sometimes they are xorg
  too.

  Performance mode is selected in nvidia-settings, which is supposed to
  mean nvidia & therefore xorg but it's not working. Selecting it
  explicitly doesn't help either.

  What is the default meant to be - probably ondemand?

  Seems like it's somehow nondeterministic. Attaching some logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+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 1931239] [NEW] System crash regulary

2021-06-08 Thread Arnold Greving

Public bug reported:

I saw the following error in the kernel log (kern.log) directly after
the crash occurred. I was watching my system with a tail -f kern.log on
a remote shell.

---

Jun  8 11:29:56 workstation kernel: [49956.666945] general protection fault, 
probably for non-canonical address 0xe365a4770fa8af10:  [#1] SMP NOPTI
Jun  8 11:29:56 workstation kernel: [49956.666958] CPU: 8 PID: 706155 Comm: git 
Tainted: G  IOE 5.11.0-18-generic #19-Ubuntu
Jun  8 11:29:56 workstation kernel: [49956.666966] Hardware name: Dell Inc. 
Precision 5820 Tower X-Series/0X75JG, BIOS 2.2.0 04/14/2020
Jun  8 11:29:56 workstation kernel: [49956.666969] RIP: 
0010:__kmalloc+0xb2/0x250
Jun  8 11:29:56 workstation kernel: [49956.666983] Code: 83 72 63 49 8b 00 49 
83 78 10 00 48 89 45 c0 0f 84 85 01 00 00 48 85 c0 0f 84 7c 01 00 00 41 8b 4c 
24 28 49 8b 3c 24 48 01 c1 <48> 8b 19 48 89 ce 49 33 9c 24 b8 00 00 00 48 8d 4a 
01 48 0f ce 48
Jun  8 11:29:56 workstation kernel: [49956.666989] RSP: :ae48650b7878 
EFLAGS: 00010282
Jun  8 11:29:56 workstation kernel: [49956.666996] RAX: e365a4770fa8aee0 RBX: 
 RCX: e365a4770fa8af10
Jun  8 11:29:56 workstation kernel: [49956.667000] RDX: 00044185 RSI: 
0d40 RDI: 000310c0
Jun  8 11:29:56 workstation kernel: [49956.667004] RBP: ae48650b78c0 R08: 
9f9c9fa310c0 R09: 0001
Jun  8 11:29:56 workstation kernel: [49956.667008] R10: 0001 R11: 
 R12: 9f8d40043a00
Jun  8 11:29:56 workstation kernel: [49956.667012] R13: 0060 R14: 
9f8d40043a00 R15: 0d40
Jun  8 11:29:56 workstation kernel: [49956.667016] FS:  7f2038755f80() 
GS:9f9c9fa0() knlGS:
Jun  8 11:29:56 workstation kernel: [49956.667021] CS:  0010 DS:  ES:  
CR0: 80050033
Jun  8 11:29:56 workstation kernel: [49956.667024] CR2: 7f2038a1c000 CR3: 
0002ac41e004 CR4: 003726e0
Jun  8 11:29:56 workstation kernel: [49956.667029] DR0:  DR1: 
 DR2: 
Jun  8 11:29:56 workstation kernel: [49956.667032] DR3:  DR6: 
fffe0ff0 DR7: 0400
Jun  8 11:29:56 workstation kernel: [49956.667036] Call Trace:
Jun  8 11:29:56 workstation kernel: [49956.667039]  ? 
ext4_find_extent+0x381/0x450
Jun  8 11:29:56 workstation kernel: [49956.667051]  ext4_find_extent+0x381/0x450
Jun  8 11:29:56 workstation kernel: [49956.667058]  
ext4_ext_map_blocks+0x72/0x980
Jun  8 11:29:56 workstation kernel: [49956.667064]  ? find_get_entry+0xcd/0x160
Jun  8 11:29:56 workstation kernel: [49956.667073]  ? find_get_entry+0xcd/0x160
Jun  8 11:29:56 workstation kernel: [49956.667080]  ? 
ext4_es_lookup_extent+0x164/0x210
Jun  8 11:29:56 workstation kernel: [49956.667087]  ext4_map_blocks+0x261/0x590
Jun  8 11:29:56 workstation kernel: [49956.667093]  ? xas_load+0x9/0x80
Jun  8 11:29:56 workstation kernel: [49956.667103]  ? xa_load+0x61/0x90
Jun  8 11:29:56 workstation kernel: [49956.667110]  
ext4_mpage_readpages+0x533/0xa70
Jun  8 11:29:56 workstation kernel: [49956.667118]  ? 
__mod_lruvec_state+0x3a/0x50
Jun  8 11:29:56 workstation kernel: [49956.667127]  ext4_readahead+0x33/0x40
Jun  8 11:29:56 workstation kernel: [49956.667132]  read_pages+0x89/0x270
Jun  8 11:29:56 workstation kernel: [49956.667140]  
page_cache_ra_unbounded+0x137/0x1f0
Jun  8 11:29:56 workstation kernel: [49956.667147]  do_page_cache_ra+0x3d/0x40
Jun  8 11:29:56 workstation kernel: [49956.667152]  
do_sync_mmap_readahead+0x10d/0x1c0
Jun  8 11:29:56 workstation kernel: [49956.667159]  filemap_fault+0x571/0x840
Jun  8 11:29:56 workstation kernel: [49956.667166]  ? xas_find+0x17a/0x1d0
Jun  8 11:29:56 workstation kernel: [49956.667172]  ? 
filemap_map_pages+0x215/0x3f0
Jun  8 11:29:56 workstation kernel: [49956.667179]  ext4_filemap_fault+0x32/0x50
Jun  8 11:29:56 workstation kernel: [49956.667185]  __do_fault+0x3c/0xe0
Jun  8 11:29:56 workstation kernel: [49956.667194]  do_fault+0xc4/0x1f0
Jun  8 11:29:56 workstation kernel: [49956.667201]  handle_pte_fault+0x1e5/0x260
Jun  8 11:29:56 workstation kernel: [49956.667207]  
__handle_mm_fault+0x599/0x7c0
Jun  8 11:29:56 workstation kernel: [49956.667216]  handle_mm_fault+0xd7/0x2b0
Jun  8 11:29:56 workstation kernel: [49956.667224]  
do_user_addr_fault+0x1a3/0x450
Jun  8 11:29:56 workstation kernel: [49956.667233]  exc_page_fault+0x6c/0x150
Jun  8 11:29:56 workstation kernel: [49956.667242]  ? 
asm_exc_page_fault+0x8/0x30
Jun  8 11:29:56 workstation kernel: [49956.667250]  asm_exc_page_fault+0x1e/0x30
Jun  8 11:29:56 workstation kernel: [49956.667256] RIP: 0033:0x7f203897399c
Jun  8 11:29:56 workstation kernel: [49956.667262] Code: 60 e9 e5 eb ff ff 0f 
1f 84 00 00 00 00 00 8d 04 31 48 01 c7 e9 4a fa ff ff 83 fb 0f 0f 87 02 09 00 
00 85 ed 0f 84 94 fb ff ff <41> 0f b6 55 00 89 d9 8d 75 ff 4d 8d 45 01 48 d3 e2 
8d 4b 08 49 01
Jun  8

[Desktop-packages] [Bug 1930887] Re: [snap] Thunderbird 78.11 does not play new email sound

2021-06-08 Thread Sebastien Bacher

Thunderbird uses libcanberra to play sound but the 3.34 gnome framework
build was not including the right driver for that to work correctly. The
issue was already fixed in 3.38 but we backported the change to 3.34
now, you should be able to verify by doing

$ sudo snap refresh --candidate gnome-3-34-1804

** Changed in: thunderbird (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [snap] Thunderbird 78.11 does not play new email sound

Status in thunderbird package in Ubuntu:
  Fix Committed

Bug description:
  (Was the same before v. 78.11.)

  TB does not play a sound when a new mail incomes, even if the correct option 
is selected.
  Changing from default to custom sound does not change the issue.

  New emails notifications do work as intended, except sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930887/+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 1931234] [NEW] package libraptor2-0 2.0.14-1 failed to install/upgrade: sub-processo dpkg-deb --fsys-tarfile retornou estado de saída de erro 2

2021-06-08 Thread Wilson Roberval Elisbon

Public bug reported:

sempre ocorre na inicialização

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libraptor2-0 2.0.14-1
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic i686
ApportVersion: 2.20.1-0ubuntu2.30
AptOrdering:
 libraptor2-0: Install
 libraptor2-0: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Sun May 30 11:07:21 2021
ErrorMessage: sub-processo dpkg-deb --fsys-tarfile retornou estado de saída de 
erro 2
InstallationDate: Installed on 2021-05-10 (28 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.7
 apt  1.2.35
SourcePackage: raptor2
Title: package libraptor2-0 2.0.14-1 failed to install/upgrade: sub-processo 
dpkg-deb --fsys-tarfile retornou estado de saída de erro 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libraptor2-0 2.0.14-1 failed to install/upgrade: sub-processo
  dpkg-deb --fsys-tarfile retornou estado de saída de erro 2

Status in raptor2 package in Ubuntu:
  New

Bug description:
  sempre ocorre na inicialização

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libraptor2-0 2.0.14-1
  ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-142-generic i686
  ApportVersion: 2.20.1-0ubuntu2.30
  AptOrdering:
   libraptor2-0: Install
   libraptor2-0: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Sun May 30 11:07:21 2021
  ErrorMessage: sub-processo dpkg-deb --fsys-tarfile retornou estado de saída 
de erro 2
  InstallationDate: Installed on 2021-05-10 (28 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.7
   apt  1.2.35
  SourcePackage: raptor2
  Title: package libraptor2-0 2.0.14-1 failed to install/upgrade: sub-processo 
dpkg-deb --fsys-tarfile retornou estado de saída de erro 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/raptor2/+bug/1931234/+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 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze

2021-06-08 Thread Jani Uusitalo

Do you want another log for that? Because (as I already mentioned
above), this also reproduces when using a newly-created user, so that
means no unsupported extensions.

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

Title:
Horizontal scroll over dock causes it to crash and disappear, and a
temporary GUI freeze

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

Bug description:
# Steps to reproduce
0. have a mouse with horizontal scrolling functionality (mine is a Microsoft
Comfort Mouse 4500 with a tilting action for horizontal scroll)
1. move mouse pointer over the dock
2. use the mouse scroller to scroll horizontally

# What I expect to happen
Nothing

# What happens
Mouse pointer and everything on screen freezes. After a few seconds it
unfreezes, but all the icons from the dock are missing. I have to log out and
back in to restore the dock.

# Other info
Slightly similar to LP #1875106, but I'm not using imwheel.

I am using Wayland.

Syslog seems to always point to this one function: "The offending
callback was get_preferred_height(), a vfunc". I'll attach the
relevant part from one crash.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 31 20:35:37 2021
InstallationDate: Installed on 2020-11-30 (182 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+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 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

2021-06-08 Thread rud

OK I can confirm: 
1. The crash has nothing to do with this error message. 
2. This error message is easy to reproduce as it happens on a clean install on 
a Fujitsu D3644-B mobo with Intel C246 chipset and Realtek ALC671 audiochip. No 
wifi or bluetooth. 

offtopic: 
regarding the crash, it is /var/crash/usr_lib_xorg_Xorg.0.crash on Ubuntu 
Budgie 21.04, BTRFS filesystem, clean install on a Lenovo S540 13-ARE Ryzen 
4800u laptop. I tried option 1 (ubuntu-bug), I get a popup and hit send. Popup 
is gone, nothing is shown in terminal. Option 2 unfortunately does not show 
anything recent has been sent in. I still have the crash file. 
I did the clean install with USB boot stick 3 times, each time I have the 
crash, same crash file, same issue not being able to send the bug in. There is 
an upload file being created in /var/crash but it is 0 bytes.

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

Title:
  Pulseaudio 14.2 says: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if the bluez error is related, perhaps not (this is a desktop
  without Wifi/Bluetooth).

  jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 
'org.bluez': timed out (service_start_timeout=25000ms)
  jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired,>

  Intel i3-9100, C246 chipset, 32GB ram.

  Ubuntu Budgie 21.04 installed via usb boot disk.

  It gives me a popup "error occured" every time I reboot..

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asterix1749 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Tue Jun  1 12:48:36 2021
  InstallationDate: Installed on 2021-05-11 (21 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.release: 1.6
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x
  dmi.board.name: D3644-B1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3644-B1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: OEM-FTS
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930409/+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 1715435] Re: Can't lock screen when using lightdm with gnome-shell

2021-06-08 Thread Jose

I managed to fix it in the following way:

1. Install dconf-editor (to edit the "registry keys")
sudo apt install dconf-editor

2. Open dconf-editor as a normal app; search for:
/org/gnome/desktop/lockdown/

3. In my case, the disable-lock-screen was set turned on. I turned it
off and everything now works fine!

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

Title:
  Can't lock screen when using lightdm with gnome-shell

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715435/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2

It might also be the compositor/WM causing leaks in Xorg. Certainly
'metacity' is second in your list, but it is meant to use a lot of
memory because it has to keep copies of all windows. To check to see if
it's the cause you would need to log into a different desktop
environment that's not Flashback.

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

Title:
  memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2

Status in libreoffice package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Progressive memory leak in Xorg. With 16Gb RAM, memory use increases
  by about 1% each day according to top. Started at about 1%, now 24%
  after nearly 3 weeks. Video driver is i915, uname -m shows x86_64.
  Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Jun  3 11:06:35 2021
  DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
   virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000]
  InstallationDate: Installed on 2017-05-31 (1463 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: GIGABYTE GB-BXi7-5500
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago)
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MQLP7AP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GB-BXi7-5500
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/+source/libreoffice/+bug/1930641/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2

2021-06-08 Thread Jan Newmarch

i don't think it is libreoffice. I last restarted X 4 days ago, and
memory usage has gone from under 1% to 8%. Libreoffice has stayed
unchanged at 459376K total (with 2 docs open). metacity has grown but
not conclusively. So I'll give it another week

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

Title:
  memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2

Status in libreoffice package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Progressive memory leak in Xorg. With 16Gb RAM, memory use increases
  by about 1% each day according to top. Started at about 1%, now 24%
  after nearly 3 weeks. Video driver is i915, uname -m shows x86_64.
  Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Jun  3 11:06:35 2021
  DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
   virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000]
  InstallationDate: Installed on 2017-05-31 (1463 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: GIGABYTE GB-BXi7-5500
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago)
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MQLP7AP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GB-BXi7-5500
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/+source/libreoffice/+bug/1930641/+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 1928360] Re: Switch to Fcitx 5 for Chinese

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

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

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Snappy:
  Invalid
Status in Ubuntu Kylin:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1928360] Re: Switch to Fcitx 5 for Chinese

On 2021-06-08 08:54, James Henstridge wrote:
>> Is there such a snap you could point me to so I can test?
> 
> The candidate channel of the gedit snap is built with core20 and the
> gnome-3-38-2004 platform snap.  But as I said, I don't think that
> platform snap currently includes the fcitx5 input module.

Right.

$ ls 
/snap/gnome-3-38-2004/current/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules 
| grep fcitx
im-fcitx.so

So then let's consider that a separate matter to be addressed later.

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

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Snappy:
  New
Status in Ubuntu Kylin:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1871351] Re: Review the vino/screen sharing situation

2021-06-08 Thread Felix Moreno

Hi, this bug is again active in ubutnu 21.04

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

Title:
  Review the vino/screen sharing situation

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

Bug description:
  g-s-d 3.36.0 removed the code to handle vino since they rely on gnome-
  remote-desktop now but we are not shipping that, we should evaluate
  what needs to be done in focal on that front

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1871351/+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 1871787] Re: Screen sharing can not be enabled from the Gnome Control Center

2021-06-08 Thread Felix Moreno

Hi this bug reapeared in ubuntu 21.04 please fix it asap.

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

Title:
  Screen sharing can not be enabled from the Gnome Control Center

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Version: Ubuntu Focal Fossa
  Package version: 1:3.36.1-1ubuntu4
  Expected: Using Screen sharing as expected and often used before
  Result: Screen sharing is disabled and can't be reenabled

  I have checked the system logs and found this entry:
  gnome-control-c[223776]: couldn't list networks: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid service name 
'vino-server'

  Then I have tried to reinstall the vino package in case that something broke 
in the update yesterday. This did not help so I tried executing the binary 
manually and this worked:
  /usr/lib/vino/vino-server 
  09/04/2020 10:16:55 Autoprobing TCP port in (all) network interface
  09/04/2020 10:16:55 Listening IPv6://[::]:5900
  09/04/2020 10:16:55 Listening IPv4://0.0.0.0:5900
  09/04/2020 10:16:55 Autoprobing selected port 5900
  09/04/2020 10:16:55 Advertising security type: 'TLS' (18)
  ... (shortened)

  The problem might be something related to DBus but I'm not shure.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  9 10:09:05 2020
  InstallationDate: Installed on 2017-11-18 (872 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-03 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871787/+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 1667894] Re: Remote desktop documenation not complete

@Felix: It should work if the gnome-remote-desktop package is installed
(which it should be by default).

Upstream issue about the need to update the documentation:

https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/124

** Bug watch added: gitlab.gnome.org/GNOME/gnome-user-docs/-/issues #124
   https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/124

** No longer affects: ubuntu-docs

** Also affects: gnome-user-docs via
   https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/124
   Importance: Unknown
   Status: Unknown

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

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

Title:
  Remote desktop documenation not complete

Status in VNC-Client:
  New
Status in Gnome Documentation:
  Unknown
Status in vino:
  New
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  The documentation on desktop sharing is incomplete. It describes how
  to turn it on but not how to use it.

  I have always been aware of this feature but I actually never tried to
  use it until today. Expecting it to just work.

  Turning sharing on is simple but it is completely unclear and
  undocumented how one would connect to the shared desktop. Remmina is
  default installed on a Ubuntu system but I don't think this is the
  software to use for this feat.

  Because the documentation is not complete I cannot use this feature. I
  have to find another way like installing VNC server.

  https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/evnc/+bug/1667894/+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 1667894] [NEW] Remote desktop documenation not complete

You have been subscribed to a public bug:

The documentation on desktop sharing is incomplete. It describes how to
turn it on but not how to use it.

I have always been aware of this feature but I actually never tried to
use it until today. Expecting it to just work.

Turning sharing on is simple but it is completely unclear and
undocumented how one would connect to the shared desktop. Remmina is
default installed on a Ubuntu system but I don't think this is the
software to use for this feat.

Because the documentation is not complete I cannot use this feature. I
have to find another way like installing VNC server.

https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html

** Affects: evnc
 Importance: Undecided
 Status: New

** Affects: gnome-user-docs
 Importance: Unknown
 Status: Unknown

** Affects: vino
 Importance: Undecided
 Status: New

** Affects: gnome-user-docs (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
Remote desktop documenation not complete
https://bugs.launchpad.net/bugs/1667894
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs in Ubuntu.

-- 
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 1928360] Re: Switch to Fcitx 5 for Chinese

2021-06-08 Thread James Henstridge

> Is there such a snap you could point me to so I can test?

The candidate channel of the gedit snap is built with core20 and the
gnome-3-38-2004 platform snap.  But as I said, I don't think that
platform snap currently includes the fcitx5 input module.

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

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Snappy:
  New
Status in Ubuntu Kylin:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1928360] Re: Switch to Fcitx 5 for Chinese