[Desktop-packages] [Bug 1936703] Re: screen keyboard doesn't work on authentication window

[Erich Eickmeyer ]

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

** Package changed: onboard (Ubuntu) => gdm (Ubuntu)

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

Title:
  screen keyboard doesn't work on authentication window

Status in gdm package in Ubuntu:
  New

Bug description:
  Before reporting the bug, lets me mention my hate about you, abandoned 
'onboard'.
  Bug description:
  pressing key on screen keyboard doesn't work on authentication window, until 
you press [Enter]. See screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 17 04:41:09 2021
  EcryptfsInUse: Yes
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
file=/cdrom/preseed/ubuntu.seed quiet splash ---
  InstallationDate: Installed on 2021-06-17 (29 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1936703/+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 1936703] [NEW] screen keyboard doesn't work on authentication window

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Before reporting the bug, lets me mention my hate about you, abandoned 
'onboard'.
Bug description:
pressing key on screen keyboard doesn't work on authentication window, until 
you press [Enter]. See screenshot

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 17 04:41:09 2021
EcryptfsInUse: Yes
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
file=/cdrom/preseed/ubuntu.seed quiet splash ---
InstallationDate: Installed on 2021-06-17 (29 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute ubiquity-is
-- 
screen keyboard doesn't work on authentication window
https://bugs.launchpad.net/bugs/1936703
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to onboard 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 1935728] Re: [radeon] Mouse pointer randomly disappears - other mouse operations still work

[Kendall Paix]

Also occurred on GNOME (I think this was on wayland also)

unity was limited functionality so didn't try for too long.

Any other suggestions?

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

Title:
  [radeon] Mouse pointer randomly disappears - other mouse operations
  still work

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  The mouse pointer randomly dissappears (same behavior in ubuntu 20.04 LTS and 
ubuntu 20.10).
  When this occurs all other mouse operations still function
  - left/right click
  - scroll wheel
  - mouse position still moves

  Just the actual mouse pointer not visible.
  Only way to resolve is to restart the machine.
  Tried numerous ways to restart the mouse driver but nothing else successful

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  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: Sat Jul 10 14:45:22 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 
4670] [1002:9488] (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6]
  InstallationDate: Installed on 2021-07-05 (4 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Apple Inc. iMac10,1
  ProcKernelCmdLine: ro root=UUID=30ee9195-f382-4721-8655-6933b38f1842 
initrd=boot\initrd.img-5.8.0-59-generic
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 215.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F2268DC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268DC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8:
  dmi.product.family: Mac
  dmi.product.name: iMac10,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  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.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/linux/+bug/1935728/+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 1927767] Re: All apps crashed in my X11 session, then terminal console crashed, reboot failed

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  All apps crashed in my X11 session, then terminal console crashed,
  reboot failed

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  The reboot failed with many services that could not stop. I think
  there may have been a crash in the network stack.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim4093 F pulseaudio
   /dev/snd/controlC2:  tim4093 F pulseaudio
   /dev/snd/controlC0:  tim4093 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 03:07:12 2021
  InstallationDate: Installed on 2020-11-22 (166 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE WIFI
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
mitigations=off crashkernel=192M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  StagingDrivers: ashmem_linux
  UpgradeStatus: Upgraded to hirsute on 2021-04-23 (14 days ago)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F33g
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITEWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITEWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ELITE WIFI
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1927767/+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 1928475] Re: Xorg freeze when booting up

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Xorg freeze when booting up

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  when booting up Ubuntu 21 it hangs for a few minutes then it becomes
  responsive it should not hang

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  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
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 14 10:42:48 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
  InstallationDate: Installed on 2021-05-14 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard HP 15 TS Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2014
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 86.26
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 TS Notebook PC
  dmi.product.sku: G9D75UA#ABA
  dmi.product.version: 097412405F0620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1928475/+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 1928420] Re: Wacom tablet tracking speed is very slow

[Launchpad Bug Tracker]

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

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

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

Title:
  Wacom tablet tracking speed is very slow

Status in mutter package in Ubuntu:
  Expired

Bug description:
  As soon as I plug in my wacom tablet. There are two pointers. 
  The real problem is after upgrading to ubuntu 21.04 The tracking speed from 
tablet i.e., pointer speed or pen speed is very slow. Please help with the 
adjustment of pointer speed from tablet.
  It might be wayland problem but we need adjustment option to work on the 
creative apps. Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 14 10:08:16 2021
  DistUpgraded: 2021-05-13 15:59:12,750 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1))
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  InstallationDate: Installed on 2016-11-07 (1648 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago)
  dmi.bios.date: 12/27/2016
  dmi.bios.release: 15.35
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 73.16
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd12/27/2016:br15.35:efr73.16:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.sku: 1JH54PC#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1
  xserver.bootTime: Wed Mar 31 09:20:55 2021
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.9-2ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1928420/+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 1928556] Re: When opened modal password input window power off button don't work

[Launchpad Bug Tracker]

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

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

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

Title:
  When opened modal password input window power off button don't work

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I opened wifi connect dialog. When I need to write password for
  network conneciton, I wish to power off notebook, but modal window
  don't allowed it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  Uname: Linux 5.11.0-18.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 15 21:36:47 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-06-28 (1051 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-12-05 (160 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300

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

[Thiago Jung Bauermann]

Em segunda-feira, 12 de julho de 2021, às 15:12:19 -03, Alex Deucher 
escreveu:
> Does the latest firmware in the firmware git tree help?
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.g
> it/log/amdgpu

I updated the picasso* files from commit:

d79c26779d45 amdgpu: update vcn firmware for green sardine for 21.20

And I still see the issue. It took a while to reproduce: I updated the 
firmware (and ran `update-initramfs -u -k all` to get it into the 
initramfs) on July 12 and had the laptop turned on since then (closing the 
lid to put it to sleep), and today I saw the problem again.

The full dmesg is attached.

** Attachment added: "dmesg.log"
   https://bugs.launchpad.net/bugs/1928393/+attachment/5511525/+files/dmesg.log

-- 
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:
  Confirmed

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 1779432]

[Robert Pearson]

Notifications are fun. But this bug has been around for more than 6 years
and has never been actually fixed. The bug is in LO since other apps *can*
print duplex. Try to *actually* FIX IT!

Robert Pearson

On Fri, Jul 16, 2021 at 9:15 AM Anand-logics <1779...@bugs.launchpad.net>
wrote:

> Is the problem really related to the software bug? There are some
> printer repair and troubleshooting tips here
> https://printerrepairhub.ae/hp-printer-repair-services-dubai
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1779432
>
> Title:
>   [upstream] Libre Writer doesn't do duplex printing
>
> Status in LibreOffice:
>   Confirmed
> Status in Ubuntu MATE:
>   Invalid
> Status in libreoffice package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The Libre Writer print settings are set to two side printing, but
>   program only prints single side. Is not HP Linux driver because both
>   FireFox and Chrome print both sides.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: libreoffice-core 1:6.0.3-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
>   Uname: Linux 4.15.0-23-generic x86_64
>   NonfreeKernelModules: ufsd
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   CurrentDesktop: MATE
>   Date: Fri Jun 29 22:17:38 2018
>   ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
>   InstallationDate: Installed on 2018-06-15 (14 days ago)
>   InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   SourcePackage: libreoffice
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+subscriptions
>
>

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

Title:
  [upstream] Libre Writer doesn't do duplex printing

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The Libre Writer print settings are set to two side printing, but
  program only prints single side. Is not HP Linux driver because both
  FireFox and Chrome print both sides.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: ufsd
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun 29 22:17:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-06-15 (14 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+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 1935818] Re: Black screen if PAM session fails to initialize completely

[Launchpad Bug Tracker]

This bug was fixed in the package gdm3 - 3.38.2.1-3ubuntu3

---
gdm3 (3.38.2.1-3ubuntu3) impish; urgency=medium

  [ Laurent Bigonville ]
  * debian/rules: Drop compatibility symlinks now that bullseye is released
  * debian/watch: Update the watch file to follow the new version scheme
  * debian/control.in: Suggest orca instead of gnome-orca, the later is a 
transitonal package

  [ Marco Trevisan (Treviño) ]
  * debian/patches:
- Refresh
- Correctly handle session opening errors (LP: #1935818)
- Emit specific error on session opened failure

 -- Marco Trevisan (Treviño)   Sat, 10 Jul 2021
18:28:45 +0200

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

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

Title:
  Black screen if PAM session fails to initialize completely

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

Bug description:
  [Description]
  If PAM session fails to initialize completely, the session aborts as expected 
but GDM stays on VT1 and switches to a black screen. This is the case for 
example, when requirement to start a session are not met and the session start 
up has to be aborted.

  [Test Plan]
  1. In /etc/pam.d/gdm-password insert the line:
  session requisite pam_deny.so
  After the line
  @include common-account
  2. Login from GDM
  3. Verify that:
    - The session fails to start
    - A black TTY is displayed
    - Active TTY is 1
  4. Apply the patched version
  5. Login from GDM
  6. Verify the login fails but GDM is still displayed and an error message in 
printed under the password box.

  [Where problem could occur]
  * Cannot login at all with any user.

  [Other info]
  * Upstream bug report and patch:
    https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/143

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdm3 3.38.2.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 12 11:36:11 2021
  InstallationDate: Installed on 2020-05-31 (407 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1935818/+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 1082110]

[timur]

Any reason this is still open?
Please add to https://wiki.documentfoundation.org/ReleaseNotes/7.2.

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

Title:
  [Upstream] Endnote placed at end of document is unmovable

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

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

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.6.2~rc2-0ubuntu4
Candidate: 1:3.6.2~rc2-0ubuntu4
Version table:
   *** 1:3.6.2~rc2-0ubuntu4 0
  900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.6.2~rc2-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages

  3) What is expected to happen in Calc is open a blank document -> type
  example -> click Insert -> Footnote/Endnote... -> under Numbering
  click radio button Automatic -> under Type click radio button Endnote
  -> click button OK and an Endnote is inserted one line down from
  example, which one may click Enter on the keyboard, moving the Endnote
  one line down, as it does in Microsoft Office Professional Plus 2010
  Word Version 14.0.6023.1000 (32-bit).

  4) What happens instead is the Endnote is placed all the way at the
  bottom of the document, and is not movable via clicking Del on the
  keyboard.

  WORKAROUND: Use AbiWord.

  apt-cache policy abiword
  abiword:
Installed: 2.9.2+svn20120603-8
Candidate: 2.9.2+svn20120603-8
Version table:
   *** 2.9.2+svn20120603-8 0
  500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages
  100 /var/lib/dpkg/status

  Open a blank document -> type example -> click References -> Insert
  Endnote and an Endnote is inserted one line down from example, which
  one may click Enter on the keyboard, moving the Endnote one line down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  Date: Thu Nov 22 09:03:21 2012
  InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1082110/+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 1936303] Re: [SRU] Debounce multiple rfkill events

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-settings-daemon -
40.0.1-1ubuntu2

---
gnome-settings-daemon (40.0.1-1ubuntu2) impish; urgency=medium

  * d/p/git-media-keys-Addd-one-second-delay-between-each-rfkill-.patch
- Add one second dely between each rfkill event (lp: #1936303)

 -- Andy Chi   Fri, 16 Jul 2021 12:09:36 +0200

** Changed in: gnome-settings-daemon (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Debounce multiple rfkill events

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  Fix Committed
Status in gnome-settings-daemon source package in Hirsute:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Some laptops can generate multiple rfkill events from a single key press.

  [Fix]
  Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second 
delay between each rfkill event").
  The commit adds a delay between each rkfill events to only process the first 
event and debounce the later ones.

  [Test]
  On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill 
events on single key press. Airplane mode will be enabled and disabled in a 
very short period, so the airplane mode cannot be turned off by the hotkey 
anymore.

  After applying the fix, pressing airplane mode hotkey can enable or
  disable airplane mode correctly.

  [Where problems could occur]
  Since the delay is hardcoded as 1 second, the airplane mode cannot be 
switched on/of in a very short time anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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 1935901] Re: Braswell video locks up under gnome-shell

[Jerry Quinn]

Hi, there's a crash report mentioned on this page:

https://errors.ubuntu.com/user/241a8d330b8560e5d29b49b2d8df1a9340834364d1e9930a70caae16e29bf446d33032781384b132361e219d11002feddb39eb224ef4a8725b7f4651d988de57

but I don't have permission to follow the link to the actual crash
report.

I originally tried using this box with X11, but I could lock up the
screen regularly.  So I tried running under wayland, which seems to be
more stable for this machine.  The above crash report is from kodi-
wayland.  When I look at what's running, I see Xwayland, which I assume
is wayland running with the x layer on top?

When I log in after a restart (too many of them), I have gnome on
wayland chosen.

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

Title:
  Braswell video locks up under gnome-shell

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I get a blank screen with a mouse cursor.  Cursor doesn't respond to
  mouse inputs.  System doesn't respond to keyboard inputs.  I can still
  ssh in from another machine.

  I see the following in the journal:

  Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer 
event3 debounce: scheduled expiry is in the past (-442ms>
  Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer 
event3 debounce short: scheduled expiry is in the past (>
  Jul 13 01:57:07 jenks gnome-shell[1403]: Failed to post KMS update: 
drmModePageFlip on CRTC 93 failed: No space left on device

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jul 13 02:06:08 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-06-29 (14 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  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/mutter/+bug/1935901/+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 1935901] Re: Braswell video locks up under gnome-shell

[Jerry Quinn]

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1935901/+attachment/5511461/+files/lspci.txt

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

Title:
  Braswell video locks up under gnome-shell

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I get a blank screen with a mouse cursor.  Cursor doesn't respond to
  mouse inputs.  System doesn't respond to keyboard inputs.  I can still
  ssh in from another machine.

  I see the following in the journal:

  Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer 
event3 debounce: scheduled expiry is in the past (-442ms>
  Jul 13 01:55:14 jenks gnome-shell[1403]: libinput error: client bug: timer 
event3 debounce short: scheduled expiry is in the past (>
  Jul 13 01:57:07 jenks gnome-shell[1403]: Failed to post KMS update: 
drmModePageFlip on CRTC 93 failed: No space left on device

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jul 13 02:06:08 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-06-29 (14 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  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/mutter/+bug/1935901/+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 1936679] [NEW] ubuntu-drivers --gpgpu is not installing -server packages

[Jeff Lane]

Public bug reported:

Discovered while testing the ubuntu-drivers-common package in -proposed
for bug LP:1898601

While waiting on bionic to deploy for verification, something was
bugging me about Focal verification from the other day so I re-deployed
a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from proposed.
What I missed when verifying the other day was that it actually isn't
installing the -server package on my server in gpgpu mode.  After
chatting a bit with Alberto, --gpgpu is supposed to install the nvidia-
driver-VER-server package. Instead, the version in -proposed is actually
installing nvidia-driver-VER which is incorrect.

Attached is a tarball from a fresh focal install that includes the
output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers
--gpgpu debug' after installing the driver.

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

** Attachment added: "ubuntu-drivers-gpgpu-focal-logs.tar"
   
https://bugs.launchpad.net/bugs/1936679/+attachment/5511458/+files/ubuntu-drivers-gpgpu-focal-logs.tar

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

Title:
  ubuntu-drivers --gpgpu is not installing -server packages

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Discovered while testing the ubuntu-drivers-common package in
  -proposed for bug LP:1898601

  While waiting on bionic to deploy for verification, something was
  bugging me about Focal verification from the other day so I re-
  deployed a DL380 with 4x T4 GPGPUs with Focal and added u-d-c from
  proposed.  What I missed when verifying the other day was that it
  actually isn't installing the -server package on my server in gpgpu
  mode.  After chatting a bit with Alberto, --gpgpu is supposed to
  install the nvidia-driver-VER-server package. Instead, the version in
  -proposed is actually installing nvidia-driver-VER which is incorrect.

  Attached is a tarball from a fresh focal install that includes the
  output when doing 'ubuntu-drivers --gpgpu install' and 'ubuntu-drivers
  --gpgpu debug' after installing the driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1936679/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

[Ken VanDine]

** Summary changed:

- NTP servers from DCHP are not propagated to timesyncd
+ NTP servers from DHCP are not propagated to timesyncd

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Heather Ellsworth (hellsworth)

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

Title:
  NTP servers from DHCP are not propagated to timesyncd

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network manager gets NTP servers from DHCP but do not update timesyncd to use 
it which keeps using ntp.ubuntu.com.
   
  This is a problem on private networks which do not have access to public 
internet. On this type of network the configuration of timesyncd must be 
updated manually instead of inheriting the conf from the dhcp servers.

  This can be integrated with a NM dispatcher script such as below:

  etc/NetworkManager/dispatcher.d/10-update-timesyncd for example:

  ==8<=8<=8<=8<=8<==
  #! /usr/bin/bash

  [ -n "$CONNECTION_UUID" ] || exit

  INTERFACE=$1
  ACTION=$2

  case $ACTION in
  up | dhcp4-change | dhcp6-change)
  [ -n "$DHCP4_NTP_SERVERS" ] || exit
  mkdir -p /etc/systemd/timesyncd.conf.d/
  cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  [Time]
  NTP=$DHCP4_NTP_SERVERS
  RootDistanceMaxSec=15
  EOF
  systemctl restart systemd-timesyncd
 ;;
  down)
  rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  systemctl restart systemd-timesyncd
  ;;
  esac
  ==8<=8<=8<=8<=8<==

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 28 14:08:52 2021
  InstallationDate: Installed on 2020-05-31 (393 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RebootRequiredPkgs:
   linux-image-5.11.0-20-generic
   linux-base
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1933828/+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 1717398] Re: incorrect file path in "/usr/share/apport/package-hooks/source_unity-settings-daemon.py"

[Sebastien Bacher]

** Changed in: unity-settings-daemon (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  incorrect file path in "/usr/share/apport/package-hooks/source_unity-
  settings-daemon.py"

Status in unity-settings-daemon package in Ubuntu:
  Fix Committed

Bug description:
  I was poking around the files for the package "unity-settings-daemon"
  and found this bug:

  in the file "/usr/share/apport/package-hooks/source_unity-settings-
  daemon.py"

  line number 6 has this typo:
  if "Stacktrace" in report and "/usr/libg/nome-settings-daemon-3.0" in 
report["Stacktrace"]:

  I guess it should be:
  if "Stacktrace" in report and "/usr/lib/gnome-settings-daemon-3.0" in 
report["Stacktrace"]:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1717398/+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 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Sebastien Bacher]

Is that still an issue with other fixes that landed?

** Changed in: pulseaudio (Ubuntu)
 Assignee: Sebastien Bacher (seb128) => (unassigned)

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  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-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1871329/+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 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system

[Gunnar Hjalmarsson]

On 2021-07-16 08:19, Kai-Heng Feng wrote:
> However, gnome-shell-extension-desktop-icons gets uninstalled on
> Impish because the gnome-shell in -proposed breaks
> gnome-shell-extension- desktop-icons (<< 21.04).

Right, and that's because the package is not (yet) adapted to GNOME 40.

I sponsored the SRUs. They are now in respective queue for review by the
SRU team.

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute)
   Status: Confirmed => In Progress

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute)
   Status: Confirmed => In Progress

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Hard to detect double-clicks on the HiDPI touchscreen system

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Focal:
  In Progress
Status in gnome-shell-extension-desktop-icons-ng source package in Focal:
  Invalid
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  In Progress
Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Impish:
  Fix Released
Status in gnome-shell-extension-desktop-icons-ng source package in Impish:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  Double tap desktop icons on a touchscreen barely works.

  [Fix]
  Because tapping isn't as precise as clicking, ignore the double click 
distance as long as the icon is tapped.

  [Test]
  Roughly double tap the desktop icon and nothing happens.
  After applying the fix, double tap can 100% open the app or directory.

  [Where problems could occur]
  If the new code throws any exception, clicking can also be affected.

  == Original Bug Report ==
  Double-clicks touchscreen on HiDPI system, sometime it will not be detected.
  Here is a related patch on upstream
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1779432] Re: [upstream] Libre Writer doesn't do duplex printing

[Norbert]

** No longer affects: ubuntu-mate

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

Title:
  [upstream] Libre Writer doesn't do duplex printing

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The Libre Writer print settings are set to two side printing, but
  program only prints single side. Is not HP Linux driver because both
  FireFox and Chrome print both sides.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: ufsd
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun 29 22:17:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-06-15 (14 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+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 1779432]

[Anand-logics]

Is the problem really related to the software bug? There are some
printer repair and troubleshooting tips here
https://printerrepairhub.ae/hp-printer-repair-services-dubai

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

Title:
  [upstream] Libre Writer doesn't do duplex printing

Status in LibreOffice:
  Confirmed
Status in Ubuntu MATE:
  Invalid
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The Libre Writer print settings are set to two side printing, but
  program only prints single side. Is not HP Linux driver because both
  FireFox and Chrome print both sides.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: ufsd
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun 29 22:17:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-06-15 (14 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+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 1936644] Re: Right-clicking on the empty trash bin in the dock results in broken empty menu

[Launchpad Bug Tracker]

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

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

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

Title:
  Right-clicking on the empty trash bin in the dock results in broken
  empty menu

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  If the trash is empty (has no deleted files), the trash bin wasn't
  open at the time, and I right-clicked on it in the dock, it would
  result in the broken empty menu that appears in the top left corner.
  Moreover, it always appears on top of every window and the top bar,
  essentially blocking the Activities button and some parts of the
  application button that shows the menu for the app.

  Steps to reproduce:
1. Log in to GNOME 40
2. Right-click on the empty trash bin in the dock (not in Nautilus)

  Expected results:
Nothing would appear.

  Actual results:
The broken empty menu in the top left corner shows up

  lsb_release -rd:
  Description:  Ubuntu Impish Indri (development branch)
  Release:  21.10

  apt-cache policy gnome-shell:
  gnome-shell:
Installed: 40.2-1ubuntu1
Candidate: 40.2-1ubuntu1
Version table:
   *** 40.2-1ubuntu1 500
  500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 16 15:26:59 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-02 (163 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
  RelatedPackageVersions: mutter-common 40.2.1-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/+source/gnome-shell/+bug/1936644/+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 1936647] [NEW] right-click popups transparent after upgrade to Firefox 90

[Kevin Otte]

Public bug reported:

Upon upgrade to Firefox 90, right-click popups appear transparent.
I am using the Blackbird gtk theme. If I switch to Adwaita-dark, the problem 
goes away.
I encountered this issue on another system with the direct download from 
Mozilla, so this is likely an upstream issue, but I'm not sure where to begin 
filing that.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 90.0+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  kjotte 1155 F pulseaudio
 /dev/snd/controlC0:  kjotte 1155 F pulseaudio
 /dev/snd/controlC1:  kjotte 1155 F pulseaudio
BuildID: 20210705185941
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: XFCE
Date: Fri Jul 16 08:35:02 2021
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-07-07 (373 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=90.0/20210705185941 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2021
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET27W (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UAS0P200
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET27W(1.17):bd03/29/2021:svnLENOVO:pn20UAS0P200:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20UAS0P200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20UAS0P200
dmi.product.sku: LENOVO_MT_20UA_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO

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


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

** Attachment added: "screenshot of transparent popup menu"
   
https://bugs.launchpad.net/bugs/1936647/+attachment/5511425/+files/firefox90-popup.png

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

Title:
  right-click popups transparent after upgrade to Firefox 90

Status in firefox package in Ubuntu:
  New

Bug description:
  Upon upgrade to Firefox 90, right-click popups appear transparent.
  I am using the Blackbird gtk theme. If I switch to Adwaita-dark, the problem 
goes away.
  I encountered this issue on another system with the direct download from 
Mozilla, so this is likely an upstream issue, but I'm not sure where to begin 
filing that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 90.0+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kjotte 1155 F pulseaudio
   /dev/snd/controlC0:  kjotte 1155 F pulseaudio
   /dev/snd/controlC1:  kjotte 1155 F pulseaudio
  BuildID: 20210705185941
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Fri Jul 16 08:35:02 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-07-07 (373 days ago)
  InstallationMedia: 

[Desktop-packages] [Bug 1936644] [NEW] Right-clicking on the empty trash bin in the dock results in broken empty menu

[EoflaOE]

Public bug reported:

If the trash is empty (has no deleted files), the trash bin wasn't open
at the time, and I right-clicked on it in the dock, it would result in
the broken empty menu that appears in the top left corner. Moreover, it
always appears on top of every window and the top bar, essentially
blocking the Activities button and some parts of the application button
that shows the menu for the app.

Steps to reproduce:
  1. Log in to GNOME 40
  2. Right-click on the empty trash bin in the dock (not in Nautilus)

Expected results:
  Nothing would appear.

Actual results:
  The broken empty menu in the top left corner shows up

lsb_release -rd:
Description:Ubuntu Impish Indri (development branch)
Release:21.10

apt-cache policy gnome-shell:
gnome-shell:
  Installed: 40.2-1ubuntu1
  Candidate: 40.2-1ubuntu1
  Version table:
 *** 40.2-1ubuntu1 500
500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 16 15:26:59 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-02-02 (163 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Broken empty menu"
   
https://bugs.launchpad.net/bugs/1936644/+attachment/5511419/+files/Ubuntu%20Daily-2021-07-16-15-26-05.png

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

Title:
  Right-clicking on the empty trash bin in the dock results in broken
  empty menu

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  If the trash is empty (has no deleted files), the trash bin wasn't
  open at the time, and I right-clicked on it in the dock, it would
  result in the broken empty menu that appears in the top left corner.
  Moreover, it always appears on top of every window and the top bar,
  essentially blocking the Activities button and some parts of the
  application button that shows the menu for the app.

  Steps to reproduce:
1. Log in to GNOME 40
2. Right-click on the empty trash bin in the dock (not in Nautilus)

  Expected results:
Nothing would appear.

  Actual results:
The broken empty menu in the top left corner shows up

  lsb_release -rd:
  Description:  Ubuntu Impish Indri (development branch)
  Release:  21.10

  apt-cache policy gnome-shell:
  gnome-shell:
Installed: 40.2-1ubuntu1
Candidate: 40.2-1ubuntu1
Version table:
   *** 40.2-1ubuntu1 500
  500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 16 15:26:59 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-02 (163 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
  RelatedPackageVersions: mutter-common 40.2.1-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/+source/gnome-shell/+bug/1936644/+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 1936643] [NEW] Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview

[EoflaOE]

Public bug reported:

In Ubuntu 21.10 Impish Indri, I have done today's updates, including
GNOME 40, and when I rebooted, I saw the desktop icons in the Activities
overview that has the grey gears icon and the gibberish name. However,
when I clicked on it, I'm taken to the desktop. When I open the
Activities overview again, that "application" didn't show up.

I suspect that this "application" came from a GNOME extension that
handles desktop icons, called gnome-shell-extension-desktop-icons-ng.
Because I thought that it loaded AFTER the Activities overview opened at
log in. This repeats every time I reboot or just log off and log back
in.

Steps to reproduce:
  1. Update the Impish system to the latest version
  2. Reboot
  3. Log in

Expected results:
  The "application" that came from the desktop icon shell extension doesn't 
appear in the Activities overview

Actual results:
  This "application" shows up in the overview with the grey gears icon and the 
gibberish name every time a user signs in to the new GNOME 40 desktop

lsb_release -rd:
Description:Ubuntu Impish Indri (development branch)
Release:21.10

apt-cache policy gnome-shell:
gnome-shell:
  Installed: 40.2-1ubuntu1
  Candidate: 40.2-1ubuntu1
  Version table:
 *** 40.2-1ubuntu1 500
500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status

If there is any more information needed, let me know.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 16 15:07:53 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-02-02 (163 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "The first screen I saw each time I log in to GNOME 40"
   
https://bugs.launchpad.net/bugs/1936643/+attachment/5511413/+files/Ubuntu%20Daily-2021-07-16-15-01-23.png

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

Title:
  Logging in to GNOME 40.2.0 causes desktop icon extension to show as
  application in Activities overview

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In Ubuntu 21.10 Impish Indri, I have done today's updates, including
  GNOME 40, and when I rebooted, I saw the desktop icons in the
  Activities overview that has the grey gears icon and the gibberish
  name. However, when I clicked on it, I'm taken to the desktop. When I
  open the Activities overview again, that "application" didn't show up.

  I suspect that this "application" came from a GNOME extension that
  handles desktop icons, called gnome-shell-extension-desktop-icons-ng.
  Because I thought that it loaded AFTER the Activities overview opened
  at log in. This repeats every time I reboot or just log off and log
  back in.

  Steps to reproduce:
1. Update the Impish system to the latest version
2. Reboot
3. Log in

  Expected results:
The "application" that came from the desktop icon shell extension doesn't 
appear in the Activities overview

  Actual results:
This "application" shows up in the overview with the grey gears icon and 
the gibberish name every time a user signs in to the new GNOME 40 desktop

  lsb_release -rd:
  Description:  Ubuntu Impish Indri (development branch)
  Release:  21.10

  apt-cache policy gnome-shell:
  gnome-shell:
Installed: 40.2-1ubuntu1
Candidate: 40.2-1ubuntu1
Version table:
   *** 40.2-1ubuntu1 500
  500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status

  If there is any more information needed, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 16 15:07:53 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-02-02 (163 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123)
  RelatedPackageVersions: mutter-common 40.2.1-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/+source/gnome-shell/+bug/1936643/+subscriptions


-- 

[Desktop-packages] [Bug 1936311] Re: Demote or remove extensions not ready for the current GNOME

[Sebastien Bacher]

** Tags removed: block-proposed block-proposed-impish impish

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

Title:
  Demote or remove extensions not ready for the current GNOME

Status in gnome-shell-extension-bluetooth-quick-connect package in Ubuntu:
  New
Status in gnome-shell-extension-caffeine package in Ubuntu:
  New
Status in gnome-shell-extension-dash-to-panel package in Ubuntu:
  New
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New
Status in gnome-shell-extension-easyscreencast package in Ubuntu:
  New
Status in gnome-shell-extension-freon package in Ubuntu:
  New
Status in gnome-shell-extension-top-icons-plus package in Ubuntu:
  New
Status in gnome-shell-extension-volume-mixer package in Ubuntu:
  New

Bug description:
  To unblock the new GNOME landing we are going to demote to propose as
  a first step, then try to follow up on
  https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from-
  universe-and-stop-auto-syncs and see which ones should be deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-bluetooth-quick-connect/+bug/1936311/+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 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

[Sebastien Bacher]

The autopkgtests worked after a retry

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test

  When you run valgrind, it will report a clean run with no writing to
  uninitialised buffers, and all invocations of glib-compile-schemas
  will be deterministic, and generate the file same with the same sha256
  hash every time. The unwritten bytes if you do a bindiff from before
  and after will be all set to zero.

  [Where problems can occur]

  I am doubtful that any programs are relying on buggy non-deterministic
  behaviour from random bytes found in uninitialised memory, so this
  should be a 

[Desktop-packages] [Bug 1936303] Re: [SRU] Debounce multiple rfkill events

[Sebastien Bacher]

** Changed in: gnome-settings-daemon (Ubuntu Impish)
   Status: Confirmed => Fix Committed

** Changed in: gnome-settings-daemon (Ubuntu Hirsute)
   Status: Confirmed => Fix Committed

** Changed in: gnome-settings-daemon (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  [SRU] Debounce multiple rfkill events

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon source package in Focal:
  Fix Committed
Status in gnome-settings-daemon source package in Hirsute:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Some laptops can generate multiple rfkill events from a single key press.

  [Fix]
  Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second 
delay between each rfkill event").
  The commit adds a delay between each rkfill events to only process the first 
event and debounce the later ones.

  [Test]
  On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill 
events on single key press. Airplane mode will be enabled and disabled in a 
very short period, so the airplane mode cannot be turned off by the hotkey 
anymore.

  After applying the fix, pressing airplane mode hotkey can enable or
  disable airplane mode correctly.

  [Where problems could occur]
  Since the delay is hardcoded as 1 second, the airplane mode cannot be 
switched on/of in a very short time anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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 1936393] Re: thunderbird window hided and abnormal context menu

[Sebastien Bacher]

** Package changed: thunderbird (Ubuntu) => gnome-shell (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/1936393

Title:
  thunderbird window hided and abnormal context menu

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Many times, when I minimize the main Thunderbird window to the dock, later, 
it's impossible to maximise it again (impossible to see it) and the contextual 
menu of the Thunderbird icon in the dock, appears on the top left of the screen 
like frozen : you can do nothing with it and you cannot hide it until you close 
the session.
  I join a screenshot

  Ubuntu 21.04 WAYLAND (64 bits)
  Thunderbird 78.11

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BuildID: 20210528153351
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 15 15:42:15 2021
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   Français Language Pack - langpack...@thunderbird.mozilla.org
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-04-10 (461 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=78.11.0/20210528153351 (In use)
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to hirsute on 2021-04-26 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1936393/+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 1936393] Re: thunderbird window hided and abnormal context menu

[Matthieu Baerts]

Hi Jean-Paul,

It looks like this issue is similar to bug 1932328.
May you check this please? If yes, please mark it as duplicated.

Cheers,
Matt

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

Title:
  thunderbird window hided and abnormal context menu

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Many times, when I minimize the main Thunderbird window to the dock, later, 
it's impossible to maximise it again (impossible to see it) and the contextual 
menu of the Thunderbird icon in the dock, appears on the top left of the screen 
like frozen : you can do nothing with it and you cannot hide it until you close 
the session.
  I join a screenshot

  Ubuntu 21.04 WAYLAND (64 bits)
  Thunderbird 78.11

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BuildID: 20210528153351
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 15 15:42:15 2021
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   Français Language Pack - langpack...@thunderbird.mozilla.org
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-04-10 (461 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=78.11.0/20210528153351 (In use)
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to hirsute on 2021-04-26 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1936393/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Sebastien Bacher]

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

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

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

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Focal:
  Fix Committed
Status in libqmi source package in Focal:
  Fix Committed
Status in modemmanager source package in Focal:
  Fix Committed
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  = Certification Validation =

  Additionally to the aforementioned test cases, the Certification Team
  will perform some coverage testing across supported devices to make
  sure the other modems still work as expected.

  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  [Other Info]

  We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  To support the mentioned 2 

[Desktop-packages] [Bug 1936303] Re: [SRU] Debounce multiple rfkill events

[Ubuntu Foundations Team Bug Bot]

The attachment "gnome-settings-daemon_3.36.1-0ubuntu1.2.debdiff" seems
to be a debdiff.  The ubuntu-sponsors team has been subscribed to the
bug report so that they can review and hopefully sponsor the debdiff.
If the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  [SRU] Debounce multiple rfkill events

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon source package in Focal:
  Confirmed
Status in gnome-settings-daemon source package in Hirsute:
  Confirmed
Status in gnome-settings-daemon source package in Impish:
  Confirmed

Bug description:
  [Impact]
  Some laptops can generate multiple rfkill events from a single key press.

  [Fix]
  Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second 
delay between each rfkill event").
  The commit adds a delay between each rkfill events to only process the first 
event and debounce the later ones.

  [Test]
  On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill 
events on single key press. Airplane mode will be enabled and disabled in a 
very short period, so the airplane mode cannot be turned off by the hotkey 
anymore.

  After applying the fix, pressing airplane mode hotkey can enable or
  disable airplane mode correctly.

  [Where problems could occur]
  Since the delay is hardcoded as 1 second, the airplane mode cannot be 
switched on/of in a very short time anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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 1936303] Re: [SRU] Debounce multiple rfkill events

[Andy Chi]

upload debdiff of impish

** Patch added: "gnome-settings-daemon_40.0.1-1ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1936303/+attachment/5511383/+files/gnome-settings-daemon_40.0.1-1ubuntu1.1.debdiff

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

Title:
  [SRU] Debounce multiple rfkill events

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon source package in Focal:
  Confirmed
Status in gnome-settings-daemon source package in Hirsute:
  Confirmed
Status in gnome-settings-daemon source package in Impish:
  Confirmed

Bug description:
  [Impact]
  Some laptops can generate multiple rfkill events from a single key press.

  [Fix]
  Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second 
delay between each rfkill event").
  The commit adds a delay between each rkfill events to only process the first 
event and debounce the later ones.

  [Test]
  On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill 
events on single key press. Airplane mode will be enabled and disabled in a 
very short period, so the airplane mode cannot be turned off by the hotkey 
anymore.

  After applying the fix, pressing airplane mode hotkey can enable or
  disable airplane mode correctly.

  [Where problems could occur]
  Since the delay is hardcoded as 1 second, the airplane mode cannot be 
switched on/of in a very short time anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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 1936303] Re: [SRU] Debounce multiple rfkill events

[Andy Chi]

upload debdiff of hirsute

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

Title:
  [SRU] Debounce multiple rfkill events

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon source package in Focal:
  Confirmed
Status in gnome-settings-daemon source package in Hirsute:
  Confirmed
Status in gnome-settings-daemon source package in Impish:
  Confirmed

Bug description:
  [Impact]
  Some laptops can generate multiple rfkill events from a single key press.

  [Fix]
  Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second 
delay between each rfkill event").
  The commit adds a delay between each rkfill events to only process the first 
event and debounce the later ones.

  [Test]
  On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill 
events on single key press. Airplane mode will be enabled and disabled in a 
very short period, so the airplane mode cannot be turned off by the hotkey 
anymore.

  After applying the fix, pressing airplane mode hotkey can enable or
  disable airplane mode correctly.

  [Where problems could occur]
  Since the delay is hardcoded as 1 second, the airplane mode cannot be 
switched on/of in a very short time anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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 1936303] Re: [SRU] Debounce multiple rfkill events

[Andy Chi]

upload debdiff for hitsute

** Patch added: "gnome-settings-daemon_3.38.1-3ubuntu3.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1936303/+attachment/5511381/+files/gnome-settings-daemon_3.38.1-3ubuntu3.2.debdiff

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

Title:
  [SRU] Debounce multiple rfkill events

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon source package in Focal:
  Confirmed
Status in gnome-settings-daemon source package in Hirsute:
  Confirmed
Status in gnome-settings-daemon source package in Impish:
  Confirmed

Bug description:
  [Impact]
  Some laptops can generate multiple rfkill events from a single key press.

  [Fix]
  Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second 
delay between each rfkill event").
  The commit adds a delay between each rkfill events to only process the first 
event and debounce the later ones.

  [Test]
  On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill 
events on single key press. Airplane mode will be enabled and disabled in a 
very short period, so the airplane mode cannot be turned off by the hotkey 
anymore.

  After applying the fix, pressing airplane mode hotkey can enable or
  disable airplane mode correctly.

  [Where problems could occur]
  Since the delay is hardcoded as 1 second, the airplane mode cannot be 
switched on/of in a very short time anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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 1936303] Re: [SRU] Debounce multiple rfkill events

[Andy Chi]

upload debdiff for focal

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: oem-priority
   Importance: Undecided => Critical

** Patch added: "gnome-settings-daemon_3.36.1-0ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1936303/+attachment/5511380/+files/gnome-settings-daemon_3.36.1-0ubuntu1.2.debdiff

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

Title:
  [SRU] Debounce multiple rfkill events

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon source package in Focal:
  Confirmed
Status in gnome-settings-daemon source package in Hirsute:
  Confirmed
Status in gnome-settings-daemon source package in Impish:
  Confirmed

Bug description:
  [Impact]
  Some laptops can generate multiple rfkill events from a single key press.

  [Fix]
  Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second 
delay between each rfkill event").
  The commit adds a delay between each rkfill events to only process the first 
event and debounce the later ones.

  [Test]
  On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill 
events on single key press. Airplane mode will be enabled and disabled in a 
very short period, so the airplane mode cannot be turned off by the hotkey 
anymore.

  After applying the fix, pressing airplane mode hotkey can enable or
  disable airplane mode correctly.

  [Where problems could occur]
  Since the delay is hardcoded as 1 second, the airplane mode cannot be 
switched on/of in a very short time anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system

[Kai-Heng Feng]

Yes, I will accomplish the testing and verification.

However, gnome-shell-extension-desktop-icons gets uninstalled on Impish
because the gnome-shell in -proposed breaks gnome-shell-extension-
desktop-icons (<< 21.04).


** Description changed:

+ == SRU Justification ==
+ [Impact]
+ Double tap desktop icons on a touchscreen barely works.
+ 
+ [Fix]
+ Because tapping isn't as precise as clicking, ignore the double click 
distance as long as the icon is tapped.
+ 
+ [Test]
+ Roughly double tap the desktop icon and nothing happens.
+ After applying the fix, double tap can 100% open the app or directory.
+ 
+ [Where problems could occur]
+ If the new code throws any exception, clicking can also be affected.
+ 
+ == Original Bug Report ==
  Double-clicks touchscreen on HiDPI system, sometime it will not be detected.
  Here is a related patch on upstream
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487

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

Title:
  Hard to detect double-clicks on the HiDPI touchscreen system

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Focal:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng source package in Focal:
  Invalid
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute:
  Confirmed
Status in gnome-shell-extension-desktop-icons source package in Impish:
  Fix Released
Status in gnome-shell-extension-desktop-icons-ng source package in Impish:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  Double tap desktop icons on a touchscreen barely works.

  [Fix]
  Because tapping isn't as precise as clicking, ignore the double click 
distance as long as the icon is tapped.

  [Test]
  Roughly double tap the desktop icon and nothing happens.
  After applying the fix, double tap can 100% open the app or directory.

  [Where problems could occur]
  If the new code throws any exception, clicking can also be affected.

  == Original Bug Report ==
  Double-clicks touchscreen on HiDPI system, sometime it will not be detected.
  Here is a related patch on upstream
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1936303] Re: [SRU] Debounce multiple rfkill events

[Andy Chi]

** Tags added: oem-priority originate-from-1929039 stella

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

Title:
  [SRU] Debounce multiple rfkill events

Status in OEM Priority Project:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon source package in Focal:
  Confirmed
Status in gnome-settings-daemon source package in Hirsute:
  Confirmed
Status in gnome-settings-daemon source package in Impish:
  Confirmed

Bug description:
  [Impact]
  Some laptops can generate multiple rfkill events from a single key press.

  [Fix]
  Commit f4dbcf3d7b0f951fe44b29229206c97b625dbfda ("media-keys: Add one second 
delay between each rfkill event").
  The commit adds a delay between each rkfill events to only process the first 
event and debounce the later ones.

  [Test]
  On HP ZBook G7, use `libinput debug-events` to observe there are two rfkill 
events on single key press. Airplane mode will be enabled and disabled in a 
very short period, so the airplane mode cannot be turned off by the hotkey 
anymore.

  After applying the fix, pressing airplane mode hotkey can enable or
  disable airplane mode correctly.

  [Where problems could occur]
  Since the delay is hardcoded as 1 second, the airplane mode cannot be 
switched on/of in a very short time anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1936303/+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