[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

[Daniel van Vugt]

Sure, try a different kernel if you know how. There's a selection at:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

Note that the current HWE kernel for 20.04 is version 5.13, not 5.11
anymore.

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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:

[Desktop-packages] [Bug 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal

[Daniel van Vugt]

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

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

Title:
  [jammy][regression] gnome-shell PolicyKit password prompt sends
   keys to the terminal

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

Bug description:
  This is a regression not seen until this week (not seen until March 4
  at least).  Calling debsign from a terminal pops up the window to
  enter the key, but the terminal is sent continuous  keys and
  the terminal scrolls down with empty input lines. You can still sign
  the file, however you end up with an empty scroll buffer if the
  signing takes too long time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1964442/+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 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal

[Alex Murray]

Upstream bug filed https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/5242

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5242
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5242

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

Title:
  [jammy][regression] gnome-shell PolicyKit password prompt sends
   keys to the terminal

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This is a regression not seen until this week (not seen until March 4
  at least).  Calling debsign from a terminal pops up the window to
  enter the key, but the terminal is sent continuous  keys and
  the terminal scrolls down with empty input lines. You can still sign
  the file, however you end up with an empty scroll buffer if the
  signing takes too long time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+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 1965219] Re: gnome lock screen does not permit reentering password

[Jeff Burdges]

I've also found folks fixed similar issues by downgrading the kernel to 
5.11.0.38:
https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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:

[Desktop-packages] [Bug 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell

[Daniel van Vugt]

It might be this: https://gitlab.gnome.org/GNOME/mutter/-/issues/2189

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2189
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2189

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

Title:
  42beta: moving mouse as screen is fading to screensaver prevents input
  to shell

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  If you move the mouse as the system fades into black for the
  screensaver, the screensaver will be prevented as normal, but the user
  will not be able to interact with the shell.

  Mouse clicks are ignored, and most key presses are ignored too.

  Workaround is to press super to enter shell overview, then super again
  to close, and mouse clicks will begin working again.

  gnome-shell 42~beta-1ubuntu2 from -proposed.

  [Testcase]

  1) Leave your system idle, until the screen starts fading to black
  2) As the screen is fading to black, move the mouse to prevent screensaver.
  3) Attempt to click any window or type something

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+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 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal

[Daniel van Vugt]

It might be related to
https://gitlab.gnome.org/GNOME/mutter/-/issues/2189 but ideally someone
should (please) open a new upstream bug to be sure:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues

** Changed in: gnome-shell (Ubuntu)
   Importance: Low => Undecided

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2189
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2189

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

Title:
  [jammy][regression] gnome-shell PolicyKit password prompt sends
   keys to the terminal

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This is a regression not seen until this week (not seen until March 4
  at least).  Calling debsign from a terminal pops up the window to
  enter the key, but the terminal is sent continuous  keys and
  the terminal scrolls down with empty input lines. You can still sign
  the file, however you end up with an empty scroll buffer if the
  signing takes too long time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+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 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal

[Alex Murray]

I personally don't think this should be low priority - this affects any
application which ends up causing the gnome shell prompt dialog to
appear - so in my case when reading my email and opening a GPG encrypted
email I get prompted for my GPG passphrase - whilst this is happening my
email client is repeatedly getting  sent to it, causing it to
advance forward to the next email and mark the current one as read - so
this has a real usability impact IMO. This is not just relevant to
terminal applications  etc.

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

Title:
  [jammy][regression] gnome-shell PolicyKit password prompt sends
   keys to the terminal

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This is a regression not seen until this week (not seen until March 4
  at least).  Calling debsign from a terminal pops up the window to
  enter the key, but the terminal is sent continuous  keys and
  the terminal scrolls down with empty input lines. You can still sign
  the file, however you end up with an empty scroll buffer if the
  signing takes too long time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+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 1965837] Re: Erroneous / extra input generated in requesting application when prompting to unlock keys

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1964442, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1964442
   [jammy][regression] gnome-shell PolicyKit password prompt sends  
keys to the terminal

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

Title:
  Erroneous / extra input generated in requesting application when
  prompting to unlock keys

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Recently I have noticed that when I am being prompted for the
  passphrase for to unlock a GPG/SSH key via the gnome-shell prompter,
  whilst the prompt is visible the requesting window seems to get
  spammed by input - this can be reproduced via running the following
  (but replace the gpg recipient with the one of your own user's private
  key):

  $ echo RELOADAGENT | gpg-connect-agent; echo foo | gpg --encrypt
  --recipient alex.mur...@canonical.com | gpg --decrypt

  See attached for a short video demonstrating the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 11:43:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-03 (230 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-01-14 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965837/+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 1965820] Re: Screen goes black when opening Settings, following error appears

[Daniel van Vugt]

I think I've seen that unhandled promise in _loadFile in other peoples'
logs too, maybe even my own. And it sounds related to a black screen,
but nobody else is reporting a black screen!?


** Summary changed:

- Screen goes black when opening Settings, following error appears
+ Screen goes black when opening Settings [Unhandled promise rejection in 
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20]

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

Title:
  Screen goes black when opening Settings [Unhandled promise rejection
  in _loadFile@resource:///org/gnome/shell/ui/background.js:503:20]

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: Unhandled promise 
rejection. To suppress this warning, add an error handler to your promise chain 
with .catch() or a try-catch block around your await expression. Stack trace of 
the failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34#012  
_monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14
  Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: message repeated 8 times: [ 
Unhandled promise rejection. To suppress this warning, add an error handler to 
your promise chain with .catch() or a try-catch block around your await 
expression. Stack trace of the failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///o]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.103.01  Thu Jan  6 
12:10:04 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 20:57:30 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Lite Hash 
Rate] [1458:404c]
  InstallationDate: Installed on 2022-03-16 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  MachineType: Gigabyte Technology Co., Ltd. B550 AORUS MASTER
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=f0d454f1-0a2b-48a3-b6ff-6ba06e951a1b ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F13h
  dmi.board.asset.tag: Default string
  dmi.board.name: B550 AORUS MASTER
  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
  

[Desktop-packages] [Bug 1965648] Re: Autorotate initiates, but doesn't reset

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1686
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1686

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

** Summary changed:

- Autorotate initiates, but doesn't reset
+ Autorotate initiates but doesn't reset in Wayland sessions (Xorg sessions 
work fine)

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

Title:
  Autorotate initiates but doesn't reset in Wayland sessions (Xorg
  sessions work fine)

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  In jammy I can get mutter's auto-rotate to switch to portrait mode
  ("right-up") by rotating the device (this only worked in impish if I
  installed the autorotate gnome-shell extension).

  However, putting it back into "normal" orientation doesn't put the
  screen back in landscape mode.  Flipping it around ("left-up") does
  swap to the reverse portrait mode, but still can't get back to
  "normal" afterward.

  running `monitor-sensor` does show the accelerometer orientation
  change events (including the "normal" ones) triggering properly, just
  the desktop doesn't respond.

  Plugging in an external monitor does seem to trigger the desktop to go
  back to normal landscape mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:41:42 2022
  InstallationDate: Installed on 2019-08-17 (945 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1965648/+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 1965820] Re: Screen goes black when opening Settings, following error appears

[Daniel van Vugt]

** Package changed: xorg (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/1965820

Title:
  Screen goes black when opening Settings, following error appears

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: Unhandled promise 
rejection. To suppress this warning, add an error handler to your promise chain 
with .catch() or a try-catch block around your await expression. Stack trace of 
the failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34#012  
_monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14
  Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: message repeated 8 times: [ 
Unhandled promise rejection. To suppress this warning, add an error handler to 
your promise chain with .catch() or a try-catch block around your await 
expression. Stack trace of the failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///o]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.103.01  Thu Jan  6 
12:10:04 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 20:57:30 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Lite Hash 
Rate] [1458:404c]
  InstallationDate: Installed on 2022-03-16 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  MachineType: Gigabyte Technology Co., Ltd. B550 AORUS MASTER
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=f0d454f1-0a2b-48a3-b6ff-6ba06e951a1b ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F13h
  dmi.board.asset.tag: Default string
  dmi.board.name: B550 AORUS MASTER
  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.:bvrF13h:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B550 MB
  dmi.product.name: B550 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: Default 

[Desktop-packages] [Bug 1965639] Re: purple screen after login using fingerprint

[Daniel van Vugt]

I can't see the cause of the problem in that log, sorry.

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

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

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

Title:
  purple screen after login using fingerprint

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I updated the machine yesterday, and additionally added the
  fingerprint to pam using pam-auth-update. The screen now stays purple
  after logging in using the finger, but works fine after logging in
  using the password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 19 21:37:43 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.103.01, 5.13.0-28-generic, x86_64: installed
   nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2294]
  InstallationDate: Installed on 2020-12-10 (464 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20NN002NGE
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=2bcb2bd8-2364-4f28-9085-f6c366d45c6d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2021
  dmi.bios.release: 1.89
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2LET89W (1.89 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NN002NGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2LET89W(1.89):bd11/24/2021:br1.89:efr1.20:svnLENOVO:pn20NN002NGE:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20NN_BU_Think_FM_ThinkPadX390Yoga:
  dmi.product.family: ThinkPad X390 Yoga
  dmi.product.name: 20NN002NGE
  dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga
  dmi.product.version: ThinkPad X390 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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/gdm3/+bug/1965639/+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 1965219] Re: gnome lock screen does not permit reentering password

[Daniel van Vugt]

Thanks for that. The log in comment #12 shows these errors which may
explain it:


Mär 22 01:57:12 aletheia systemd[1]: systemd-logind.service: Watchdog timeout 
(limit 3min)!
Mär 22 01:57:12 aletheia systemd[1]: systemd-logind.service: Killing process 
1501 (systemd-logind) with signal SIGABRT.
...
Mär 22 01:57:12 aletheia systemd[1]: systemd-logind.service: Main process 
exited, code=killed, status=6/ABRT
...
Mär 22 01:57:13 aletheia /usr/lib/gdm3/gdm-x-session[2486]: (EE)
Mär 22 01:57:13 aletheia /usr/lib/gdm3/gdm-x-session[2486]: Fatal server error:
Mär 22 01:57:13 aletheia /usr/lib/gdm3/gdm-x-session[2486]: (EE) 
systemd-logind disappeared (stopped/restarted?)
...
Mär 22 01:57:13 aletheia systemd-logind[95934]: Failed to restore VT, 
ignoring: Bad file descriptor


And yes we expect "Fn+Ctrl+Alt+F??" to fail in this case because the
processes which implement that combo have failed.

To be sure we're on the right track, please reboot, wait for the bug to
occur again, and then redo:

  journalctl -b-1 > prevboot.txt

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

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

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 

[Desktop-packages] [Bug 1965537] Re: Desktop Icons NG gjs high CPU ussage when moving window

[Daniel van Vugt]

Also assigned to gnome-shell/mutter since it sounds like the problem is
originating there (comment #10).

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

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

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

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

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

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

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

Title:
  Desktop Icons NG gjs high CPU ussage when moving window

Status in Gnome Shell Extension Desktop Icons Ng:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Desktop Icons NG gjs high CPU usage when moving window - check
  enclosed video. When I disable Desktop Icons NG extensions CPU usage
  is fine.

  System spec:
  Intel® Core™ i7-2600 CPU @ 3.40GHz × 8
  AMD® Radeon rx 560 series
  Wayland
  Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1965537/+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 1965648] Re: Autorotate initiates, but doesn't reset

[Joe Barnett]

One more piece of information in a wayland session:  If I fully fold the
device into tablet mode, then I can rotate back and forth successfully,
it only gets stuck if I go back into laptop mode.

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

Title:
  Autorotate initiates, but doesn't reset

Status in mutter package in Ubuntu:
  New

Bug description:
  In jammy I can get mutter's auto-rotate to switch to portrait mode
  ("right-up") by rotating the device (this only worked in impish if I
  installed the autorotate gnome-shell extension).

  However, putting it back into "normal" orientation doesn't put the
  screen back in landscape mode.  Flipping it around ("left-up") does
  swap to the reverse portrait mode, but still can't get back to
  "normal" afterward.

  running `monitor-sensor` does show the accelerometer orientation
  change events (including the "normal" ones) triggering properly, just
  the desktop doesn't respond.

  Plugging in an external monitor does seem to trigger the desktop to go
  back to normal landscape mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:41:42 2022
  InstallationDate: Installed on 2019-08-17 (945 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+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 1942789] Re: On-demand and RTD3 need to be separated

[Chris Halse Rogers]

Hello jeremyszu, or anyone else affected,

Accepted nvidia-prime into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
prime/0.8.16~0.20.04.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: nvidia-prime (Ubuntu Focal)
   Status: Incomplete => Fix Committed

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

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

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Hirsute:
  Won't Fix

Bug description:
  RTD3 is a nvidia GPU feature to support runtime suspend.

  On-demand would be a X offloading feature.

  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.

  Some parts need to be adjusted, e.g.

  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass

  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * Old GPU (which supported by nvidia-390 only) will keep in performance 
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * With GPU supported RTD3 not able enable runtime PM on non-laptop.
  But based on the Nvidia README, this case shall not happened.

  [Other Info]

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Handle BrokenPipeError (LP: #1965520).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1942788] Re: Nvidia doesn't support RTD3 on non-laptops

[Chris Halse Rogers]

Hello jeremyszu, or anyone else affected,

Accepted nvidia-prime into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
prime/0.8.16~0.20.04.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: nvidia-prime (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  Nvidia doesn't support RTD3 on non-laptops

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in nvidia-prime source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  Fix Released

Bug description:
  According to Nvidia README, the RTD3 doesn't support on non-laptop
  machine.

  https://github.com/tseliot/ubuntu-drivers-common/issues/55

  We need to check chassis type before enabling RTD3.

  ---

  [Impact]

   * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
   * Patch make system not enable RTD3 unless it's a laptop

  [Test Plan]

   * Install Ubuntu on machine
   * Install GPU driver via 'ubuntu-drivers install'
   * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created

  [Where problems could occur]

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

  [Other Info]

  Information for Focal, refer to
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942788/+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 1946476] Re: New on-demand default causes RTD3 never to be enabled

[Chris Halse Rogers]

Hello Alberto, or anyone else affected,

Accepted nvidia-prime into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
prime/0.8.16~0.20.04.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: nvidia-prime (Ubuntu Focal)
   Status: Incomplete => Fix Committed

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

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

Title:
  New on-demand default causes RTD3 never to be enabled

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Hirsute:
  Incomplete
Status in nvidia-prime source package in Impish:
  Fix Released

Bug description:
  As per LP: #1942307 we now set on-demand as the default. This however,
  causes "prime-select on-demand", called by ubuntu-drivers, not to even
  try to detect RTD3 and to enable it, since "on-demand" is already set.

  We cannot make informed choices about RTD3 in the postinstallation
  script of nvidia-prime, therefore we should simply drop the check that
  prime-select makes to abort if the new profile is determined to be the
  same as the current profile.

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * Old GPU (which supported by nvidia-390 only) will keep in performance 
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * With GPU supported RTD3 not able enable runtime PM on non-laptop.
  But based on the Nvidia README, this case shall not happened.

  [Other Info]

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Handle BrokenPipeError (LP: #1965520).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946476/+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 1965520] Re: /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime-select@374:enable_profile:_disable_nvidia:_update_initramfs

[Chris Halse Rogers]

Hello errors.ubuntu.com, or anyone else affected,

Accepted nvidia-prime into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
prime/0.8.16~0.20.04.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: nvidia-prime (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime-
  select@374:enable_profile:_disable_nvidia:_update_initramfs

Status in nvidia-prime package in Ubuntu:
  Triaged
Status in nvidia-prime source package in Bionic:
  Triaged
Status in nvidia-prime source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * The progress bar that is drawn to keep track of the update-
  initramfs process can result, sometimes, in a BrokenPipe error. In no
  way does this affect the final result of the actual operation, yet it
  causes the progress bar to crash.

  [Test Plan]

   * Install the nvidia-prime package and , and then execute "sudo
  prime-select intel" so that NVIDIA can be disabled, and the update-
  initramfs command is called. This might need repeating (i.e. going
  back and forth from "sudo prime-select intel" to "sudo prime-select
  on-demand" until the BrokenPipe error shows up.

  [Where problems could occur]

   * This can cause no regression, since it does not alter the actual
  functioning on nvidia-prime, and the change has been in Impish since
  its release.

  [Other Info]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1965520/+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 1942307] Re: ubiquity uses performance mode for nvidia driver

[Chris Halse Rogers]

Hello jeremyszu, or anyone else affected,

Accepted nvidia-prime into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
prime/0.8.16~0.20.04.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: nvidia-prime (Ubuntu Focal)
   Status: Incomplete => Fix Committed

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

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

Title:
  ubiquity uses performance mode for nvidia driver

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Hirsute:
  Incomplete

Bug description:
  [Steps to reproduce]
  1. Install 20.04.3 with "Third-party packages" on a system which containing a 
RTD3 supported nvidia card.
  2. After the installation, press enter to reboot system
  3. prime-select query

  [Expected result]
  on-demand

  [Actual result]
  performance

  ---

  It's because ubiquity launches `ubuntu-drivers install --packages-list
  ...` in live system but install each package to target storage.

  When installing nvidia-prime, the preinst set "on" to "/etc/prime-
  discrete" which will be referred by gpu-manager. The gpu-manager will
  set to performance mode.

  After confirming with Alberto on Mattermost, since we don't have a
  nvidia driver which lower than 450 version since focal.

  I think we are ok to switch to on-demand mode.

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * Old GPU (which supported by nvidia-390 only) will keep in performance 
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * With GPU supported RTD3 not able enable runtime PM on non-laptop.
  But based on the Nvidia README, this case shall not happened.

  [Other Info]

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)

[ Alberto Milone ]
* prime-select:
  - Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
  - Don't check the current profile when setting
a profile (LP: #1946476).
  - Handle BrokenPipeError (LP: #1965520).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942307/+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 1942789] Re: On-demand and RTD3 need to be separated

[Dirk Su]

** Description changed:

  RTD3 is a nvidia GPU feature to support runtime suspend.
  
  On-demand would be a X offloading feature.
  
  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.
  
  Some parts need to be adjusted, e.g.
  
  ```
- # If we are dealing with NVIDIA PRIME, and runtimepm
- # is supported, enable it
- if (os.path.isfile('/run/nvidia_runtimepm_supported') and
- os.path.isfile('/usr/bin/prime-select')):
- print('Trying to select the on-demand PRIME profile')
- try:
- subprocess.call(['prime-select', 'on-demand'])
- except:
- pass
+ # If we are dealing with NVIDIA PRIME, and runtimepm
+ # is supported, enable it
+ if (os.path.isfile('/run/nvidia_runtimepm_supported') and
+ os.path.isfile('/usr/bin/prime-select')):
+ print('Trying to select the on-demand PRIME profile')
+ try:
+ subprocess.call(['prime-select', 'on-demand'])
+ except:
+ pass
  
- # Create the override file for gpu-manager
- with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
- f.write('# File created by ubuntu-drivers\n')
+ # Create the override file for gpu-manager
+ with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
+ f.write('# File created by ubuntu-drivers\n')
  ```
- 
  
  ---
  
  [Impact]
  
   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * Old GPU (which supported by nvidia-390 only) will keep in performance 
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But
  based on the Nvidia README, this case shall not happened.
  
  [Other Info]
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)
  
    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
- - Catch BrokenPipeError.
- - Use bootvga detection when last_gfx_boot is
-   not available.
+ - Handle BrokenPipeError (LP: #1965520).

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

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Incomplete
Status in nvidia-prime source package in Hirsute:
  Won't Fix

Bug description:
  RTD3 is a nvidia GPU feature to support runtime suspend.

  On-demand would be a X offloading feature.

  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.

  Some parts need to be adjusted, e.g.

  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass

  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * Old GPU (which supported by nvidia-390 only) will keep in 

[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled

[Dirk Su]

** Description changed:

  As per LP: #1942307 we now set on-demand as the default. This however,
  causes "prime-select on-demand", called by ubuntu-drivers, not to even
  try to detect RTD3 and to enable it, since "on-demand" is already set.
  
  We cannot make informed choices about RTD3 in the postinstallation
  script of nvidia-prime, therefore we should simply drop the check that
  prime-select makes to abort if the new profile is determined to be the
  same as the current profile.
- 
  
  ---
  
  [Impact]
  
   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * Old GPU (which supported by nvidia-390 only) will keep in performance 
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But
  based on the Nvidia README, this case shall not happened.
  
  [Other Info]
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)
  
    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
- - Catch BrokenPipeError.
- - Use bootvga detection when last_gfx_boot is
-   not available.
+ - Handle BrokenPipeError (LP: #1965520).

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

Title:
  New on-demand default causes RTD3 never to be enabled

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Incomplete
Status in nvidia-prime source package in Hirsute:
  Incomplete
Status in nvidia-prime source package in Impish:
  Fix Released

Bug description:
  As per LP: #1942307 we now set on-demand as the default. This however,
  causes "prime-select on-demand", called by ubuntu-drivers, not to even
  try to detect RTD3 and to enable it, since "on-demand" is already set.

  We cannot make informed choices about RTD3 in the postinstallation
  script of nvidia-prime, therefore we should simply drop the check that
  prime-select makes to abort if the new profile is determined to be the
  same as the current profile.

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * Old GPU (which supported by nvidia-390 only) will keep in performance 
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * With GPU supported RTD3 not able enable runtime PM on non-laptop.
  But based on the Nvidia README, this case shall not happened.

  [Other Info]

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Handle BrokenPipeError (LP: #1965520).

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


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

[Desktop-packages] [Bug 1965837] Re: Erroneous / extra input generated in requesting application when prompting to unlock keys

[Alex Murray]

If it is not clear from the video - watch the terminal window in the
background when the prompt for the passphrase appears - it keeps
scrolling as though getting input by newlines all the time - and this
then persists even after the prompt is dismissed until I manually
provide some input myself.

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

Title:
  Erroneous / extra input generated in requesting application when
  prompting to unlock keys

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Recently I have noticed that when I am being prompted for the
  passphrase for to unlock a GPG/SSH key via the gnome-shell prompter,
  whilst the prompt is visible the requesting window seems to get
  spammed by input - this can be reproduced via running the following
  (but replace the gpg recipient with the one of your own user's private
  key):

  $ echo RELOADAGENT | gpg-connect-agent; echo foo | gpg --encrypt
  --recipient alex.mur...@canonical.com | gpg --decrypt

  See attached for a short video demonstrating the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 11:43:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-03 (230 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-01-14 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965837/+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 1965837] [NEW] Erroneous / extra input generated in requesting application when prompting to unlock keys

[Alex Murray]

Public bug reported:

Recently I have noticed that when I am being prompted for the passphrase
for to unlock a GPG/SSH key via the gnome-shell prompter, whilst the
prompt is visible the requesting window seems to get spammed by input -
this can be reproduced via running the following (but replace the gpg
recipient with the one of your own user's private key):

$ echo RELOADAGENT | gpg-connect-agent; echo foo | gpg --encrypt
--recipient alex.mur...@canonical.com | gpg --decrypt

See attached for a short video demonstrating the issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 22 11:43:36 2022
DisplayManager: gdm3
InstallationDate: Installed on 2021-08-03 (230 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-01-14 (66 days ago)

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


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

** Attachment added: "Screencast from 22-03-22 11:45:41.webm"
   
https://bugs.launchpad.net/bugs/1965837/+attachment/5571537/+files/Screencast%20from%2022-03-22%2011%3A45%3A41.webm

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

Title:
  Erroneous / extra input generated in requesting application when
  prompting to unlock keys

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Recently I have noticed that when I am being prompted for the
  passphrase for to unlock a GPG/SSH key via the gnome-shell prompter,
  whilst the prompt is visible the requesting window seems to get
  spammed by input - this can be reproduced via running the following
  (but replace the gpg recipient with the one of your own user's private
  key):

  $ echo RELOADAGENT | gpg-connect-agent; echo foo | gpg --encrypt
  --recipient alex.mur...@canonical.com | gpg --decrypt

  See attached for a short video demonstrating the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 11:43:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-03 (230 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-01-14 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965837/+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 1965219] Re: gnome lock screen does not permit reentering password

[Jeff Burdges]

I've also found folks fixed similar issues by downgrading the kernel to 
5.11.0.38:
https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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:

[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

[Jeff Burdges]

Also the Fn+Ctrl+Alt+F?? keys no longer worked here.

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

[Jeff Burdges]

I'd something new this time, after sleep/suspend it returned to the
purple login screen, but now nothing worked, no mouse or keyboard.  It
ran the fan for a little while, so I give it some time to return, but no
luck.

** Attachment added: "purple_no_mouse.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5571532/+files/purple_no_mouse.txt

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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
  

[Desktop-packages] [Bug 1963264] Re: Screencast not recording

[Joe Barnett]

I had pipewire-media-session libpipewire-0.3-common installed fine after
an upgrade from impish->jammy, but still had to remove the
libgstpipewire so, and reinstall the package to get gstreamer to
recognize the pipewiresrc element

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

Title:
  Screencast not recording

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  When I press Ctrl+Shift+Alt+R, screencast indicator appears in the
  indicator menu but disappears in about 2 seconds. No file is even
  created under the Videos folder.

  journalctl shows:

  Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] 
Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' 
(uid=1000 pid=3311 comm="/usr/libexec/gsd-media->
  Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] 
Successfully activated service 'org.gnome.Shell.Screencast'
  Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] 
Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' 
(uid=1000 pid=3311 comm="/usr/libexec/gsd-media->
  Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] 
Successfully activated service 'org.gnome.Shell.Screencast'
  Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: 
Gst.ParseError: no element "pipewiresrc"
   
  The issue is the Gst.ParseError.

  Before upgrading to jammy (22.04), it used to work fine. Also, when
  testing under qemu/KVM it works properly. It just doesn't work when
  running directly on the PC.

  What other logs can I provide?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  3 15:41:44 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-12 (660 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 41.3-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+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 1964546] Re: 1Password doesn't integrate with Firefox Snap

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1741074
   [snap] chrome-gnome-shell extension fails to detect native host connector

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

Title:
  1Password doesn't integrate with Firefox Snap

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I use for sometime now 1Password for Linux on Ubuntu. 1Password
  integrates with the 1Password Firefox extension, but just when using
  Deb version. The most visible integration is to unlock via browser
  extension, which calls the desktop application to enter the password.
  The Firefox Snap doesn't have this integration yet, probably because
  the extension can't talk with the desktop application. The problem is
  in Jammy-proposed is forcing to adopt Firefox Snap version, but I want
  to keep using Firefox Deb version until this problem is fixed, so one
  of two ways: or we find a way to integrate 1Password desktop app with
  Firefox Snap or create a package alternative to people who want to
  keep using Firefox Deb for this or any other limitation of Firefox
  Snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964546/+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 1965809] Re: 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with SIGSEGV in g_slice_alloc()

[XA Hydra]

** Information type changed from Private to Public

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

Title:
   22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem
  crashed with SIGSEGV in g_slice_alloc()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Attempting to open videos in multiple formats (tried .webm and .mp4 so
  far) results in ‘specified movie could not be found’ errors in Videos.

  I’ve moved them into multiple folders with the same result. If I hit
  the upper left button ’ < ’ I can see the file just fine

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer1.0-0 1.20.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 14:20:08 2022
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2022-02-17 (32 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f023771dd0c :mov
0x8(%r12),%rax
   PC (0x7f023771dd0c) ok
   source "0x8(%r12)" (0x55e51814962008) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: totem crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1965809/+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 1965648] Re: Autorotate initiates, but doesn't reset

[Joe Barnett]

The bug does not appear to occur under Xorg sessions:

 - Ubuntu on Xorg: rotated back and forth numerous times successfully
 - Ubuntu: rotated back and forth once successfully and then got stuck in 
portrait mode
 - Gnome on Xorg: rotated back and forth numerous times successfully
 - Gnome: rotated back and forth once successfully and then got stuck in 
portrait mode

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+attachment/5571502/+files/journal.txt

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

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

Title:
  Autorotate initiates, but doesn't reset

Status in mutter package in Ubuntu:
  New

Bug description:
  In jammy I can get mutter's auto-rotate to switch to portrait mode
  ("right-up") by rotating the device (this only worked in impish if I
  installed the autorotate gnome-shell extension).

  However, putting it back into "normal" orientation doesn't put the
  screen back in landscape mode.  Flipping it around ("left-up") does
  swap to the reverse portrait mode, but still can't get back to
  "normal" afterward.

  running `monitor-sensor` does show the accelerometer orientation
  change events (including the "normal" ones) triggering properly, just
  the desktop doesn't respond.

  Plugging in an external monitor does seem to trigger the desktop to go
  back to normal landscape mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:41:42 2022
  InstallationDate: Installed on 2019-08-17 (945 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+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 1965820] [NEW] Screen goes black when opening Settings, following error appears

[David]

Public bug reported:

Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: Unhandled promise rejection. 
To suppress this warning, add an error handler to your promise chain with 
.catch() or a try-catch block around your await expression. Stack trace of the 
failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34#012  
_monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14
Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: message repeated 8 times: [ 
Unhandled promise rejection. To suppress this warning, add an error handler to 
your promise chain with .catch() or a try-catch block around your await 
expression. Stack trace of the failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///o]

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.103.01  Thu Jan  6 
12:10:04 UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 21 20:57:30 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Lite Hash 
Rate] [1458:404c]
InstallationDate: Installed on 2022-03-16 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
MachineType: Gigabyte Technology Co., Ltd. B550 AORUS MASTER
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=f0d454f1-0a2b-48a3-b6ff-6ba06e951a1b ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F13h
dmi.board.asset.tag: Default string
dmi.board.name: B550 AORUS MASTER
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.:bvrF13h:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B550 MB
dmi.product.name: B550 AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 

[Desktop-packages] [Bug 1965813] Re: gnome-control-center crashed with SIGSEGV while setting google accout @ control center

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1965702, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1965813/+attachment/5571433/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1965813/+attachment/5571435/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1965813/+attachment/5571439/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1965813/+attachment/5571440/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1965813/+attachment/5571441/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965813/+attachment/5571442/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965813/+attachment/5571443/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1965702

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV while setting google accout
  @ control center

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Probably the case with 22.04

  Newly installed system refusues to log in to google account.
  Everything was fine in 21.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu8
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 22:00:19 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-03-20 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  ProcCmdline: gnome-control-center
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7f341950130b:mov0x8,%rax
   PC (0x7f341950130b) ok
   source "0x8" (0x0008) not located in a known VMA region (needed readable 
region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
   ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965813/+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 1965811] [NEW] software-properties-qt does not load driver information

[Erich Eickmeyer ]

Public bug reported:

Driver information is not being loaded by software-properties-qt. This
appears to be a python issue, perhaps a python 3.10 compatibility issue.

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1024, in detect_drivers
self.devices = detect.system_device_drivers(self.apt_cache)
  File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in 
system_device_drivers
for pkg, pkginfo in system_driver_packages(apt_cache, sys_path,
  File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in 
system_driver_packages
for p in packages_for_modalias(apt_cache, alias):
  File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in 
packages_for_modalias
apt_cache_hash = hash(package.get_fullname() for package in 
apt_cache.packages)
AttributeError: 'Cache' object has no attribute 'packages'
Exception ignored in: 

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-qt 0.99.19
ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
Uname: Linux 5.15.0-22-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Mon Mar 21 11:34:54 2022
InstallationDate: Installed on 2021-03-20 (365 days ago)
InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to jammy on 2021-11-07 (134 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Critical
 Status: New

** Affects: software-properties (Ubuntu Jammy)
 Importance: Critical
 Status: New


** Tags: amd64 apport-bug jammy

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Critical

** Also affects: software-properties (Ubuntu Jammy)
   Importance: Critical
   Status: New

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

Title:
  software-properties-qt does not load driver information

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Jammy:
  New

Bug description:
  Driver information is not being loaded by software-properties-qt. This
  appears to be a python issue, perhaps a python 3.10 compatibility
  issue.

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1024, in detect_drivers
  self.devices = detect.system_device_drivers(self.apt_cache)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in 
system_device_drivers
  for pkg, pkginfo in system_driver_packages(apt_cache, sys_path,
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in 
system_driver_packages
  for p in packages_for_modalias(apt_cache, alias):
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in 
packages_for_modalias
  apt_cache_hash = hash(package.get_fullname() for package in 
apt_cache.packages)
  AttributeError: 'Cache' object has no attribute 'packages'
  Exception ignored in: 

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-qt 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Mar 21 11:34:54 2022
  InstallationDate: Installed on 2021-03-20 (365 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (134 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965811/+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 1965812] [NEW] After "apt upgrade" around Mar 18, shotwell desktop slideshow does not work any more

[Haitao Shan]

Public bug reported:

Hi,

I had ubuntu 22.04, which was upgraded from 21.10 following the link:
https://linuxconfig.org/how-to-upgrade-ubuntu-to-22-04-lts-jammy-
jellyfish. It has worked well for me until I run "apt update and apt
upgrade" around Mar 18. I have wallpaper slideshow setup using shotwell
before the upgrade. I noticed my desktop background went to black after
the upgrade. I then logged out and logged in. The background was changed
to an Ubuntu default. I tried to set desktop slideshow again using
shotwell but it never worked any more. From the GUI, I did not see
anything abnormal. But the desktop background simply did not change at
all.

I guess something was broken by one of the upgraded packages.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: shotwell 0.30.14-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 21 11:29:40 2022
InstallationDate: Installed on 2021-08-27 (205 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: shotwell
UpgradeStatus: Upgraded to jammy on 2022-02-08 (41 days ago)

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


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

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

Title:
  After "apt upgrade" around Mar 18, shotwell desktop slideshow does not
  work any more

Status in shotwell package in Ubuntu:
  New

Bug description:
  Hi,

  I had ubuntu 22.04, which was upgraded from 21.10 following the link:
  https://linuxconfig.org/how-to-upgrade-ubuntu-to-22-04-lts-jammy-
  jellyfish. It has worked well for me until I run "apt update and apt
  upgrade" around Mar 18. I have wallpaper slideshow setup using
  shotwell before the upgrade. I noticed my desktop background went to
  black after the upgrade. I then logged out and logged in. The
  background was changed to an Ubuntu default. I tried to set desktop
  slideshow again using shotwell but it never worked any more. From the
  GUI, I did not see anything abnormal. But the desktop background
  simply did not change at all.

  I guess something was broken by one of the upgraded packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: shotwell 0.30.14-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 11:29:40 2022
  InstallationDate: Installed on 2021-08-27 (205 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shotwell
  UpgradeStatus: Upgraded to jammy on 2022-02-08 (41 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1965812/+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 1958224] Re: brltty claiming cp210x devices on 22.04

[Samuel thibault]

> In this case, brltty appeared (or at least the device claim) after a
dist-upgrade

Ah, do you happen to have a log of that dist-upgrade, so we can
determine what brought it in?

> It still feels very bad form for a vendor device to use the default
VID/PID of the underlying converter chip

Yes. Unfortunately that's what they have done, those devices are out
there, and people have already bought them (and they cost a lot of
money) :(

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

Title:
  brltty claiming cp210x devices on 22.04

Status in brltty package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  brltty:  Installed: 6.4-2ubuntu1

   brltty appears once again to be claiming cp210x devices with the
  vendor/product ID of:

  idVendor=10c4, idProduct=ea60

  Example dmesg output:
999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [  999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
  [  999.215977] usb 3-6.3: Manufacturer: Silicon Labs
  [  999.215978] usb 3-6.3: SerialNumber: 0005
  [  999.234070] usbcore: registered new interface driver usbserial_generic
  [  999.234081] usbserial: USB Serial support registered for generic
  [  999.235262] usbcore: registered new interface driver cp210x
  [  999.235272] usbserial: USB Serial support registered for cp210x
  [  999.235298] cp210x 3-6.3:1.0: cp210x converter detected
  [  999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
  [  999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
  [  999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input42
  [  999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [  999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [  999.995066] cp210x 3-6.3:1.0: device disconnected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+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 1958224] Re: brltty claiming cp210x devices on 22.04

[bdav]

In this case, brltty appeared (or at least the device claim) after a
dist-upgrade. I would have had no cause to use it through the initial
installation.

It still feels very bad form for a vendor device to use the default
VID/PID of the underlying converter chip as opposed to the (very easy)
step of changing it in the case of the cp210x.

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

Title:
  brltty claiming cp210x devices on 22.04

Status in brltty package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  brltty:  Installed: 6.4-2ubuntu1

   brltty appears once again to be claiming cp210x devices with the
  vendor/product ID of:

  idVendor=10c4, idProduct=ea60

  Example dmesg output:
999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [  999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
  [  999.215977] usb 3-6.3: Manufacturer: Silicon Labs
  [  999.215978] usb 3-6.3: SerialNumber: 0005
  [  999.234070] usbcore: registered new interface driver usbserial_generic
  [  999.234081] usbserial: USB Serial support registered for generic
  [  999.235262] usbcore: registered new interface driver cp210x
  [  999.235272] usbserial: USB Serial support registered for cp210x
  [  999.235298] cp210x 3-6.3:1.0: cp210x converter detected
  [  999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
  [  999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
  [  999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input42
  [  999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [  999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [  999.995066] cp210x 3-6.3:1.0: device disconnected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+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 1962556] Re: [FFe] WSL systemd experimental support

[Launchpad Bug Tracker]

This bug was fixed in the package wsl-setup - 0.2

---
wsl-setup (0.2) jammy; urgency=medium

  * Systemd experimental support (LP: #1962556)

 -- Didier Roche   Thu, 17 Mar 2022 16:08:44 +0100

** Changed in: wsl-setup (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [FFe] WSL systemd experimental support

Status in wsl-setup package in Ubuntu:
  Fix Released

Bug description:
  WSL on Ubuntu 22.04 has a strecth goal to ship systemd experimental support.
  This relies on 3 changes:
  - a script started up on WSL VM boot, which is shipped as part of this 
package to start systemd in its own namespace.
  - a change in the ubuntu Windows launcher executable, which is then looking 
for the boot= parameter in wsl.conf and if systemd experimental support is 
enabled, starts any new commands into that systemd namespace
  - an option in our OOBE installer, under advanced menu, disabled by default, 
to change the boot= parameter in wsl.conf. The feature will be labeled as 
experimental.

  So, this experimental support won’t be enabled by default and paved the way 
to have a discussion with Microsoft for potential limitations and how we can 
get this to a wider audience in the long term.
  This feature is long-awaited for WSL users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/1962556/+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 1964546] Re: 1Password doesn't integrate with Firefox Snap

[Launchpad Bug Tracker]

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

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

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

Title:
  1Password doesn't integrate with Firefox Snap

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I use for sometime now 1Password for Linux on Ubuntu. 1Password
  integrates with the 1Password Firefox extension, but just when using
  Deb version. The most visible integration is to unlock via browser
  extension, which calls the desktop application to enter the password.
  The Firefox Snap doesn't have this integration yet, probably because
  the extension can't talk with the desktop application. The problem is
  in Jammy-proposed is forcing to adopt Firefox Snap version, but I want
  to keep using Firefox Deb version until this problem is fixed, so one
  of two ways: or we find a way to integrate 1Password desktop app with
  Firefox Snap or create a package alternative to people who want to
  keep using Firefox Deb for this or any other limitation of Firefox
  Snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964546/+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 1964095] Re: print sent to Epson ET-2810 is not printed

[Jan Mathisen]

OK  I printed two files successfully with:

jbm@curlew:~/test_set$ lp Truloc-211-Retainer.pdf
request id is jbm-2810-314 (1 file(s))
jbm@curlew:~/test_set$ lp IMG_4737x.JPG
request id is jbm-2810-315 (1 file(s))

The files are enclosed, together with the subsequent error_log.
The Trulocpdf file should be the same one that failed whem sent from 
Document Viewer.

On 2022-03-21 17:44, Till Kamppeter wrote:
> I your error_log I have found the following:
>
> D [21/Mar/2022:15:08:48 +0100] [Job 312] Send-Document: client-error-
> document-format-error (client-error-document-format-error)
>
> This looks like that the printer was not able to work with the data it
> received.
>
> The printer reports that it accepts PWG Raster as the only of the known
> data formats used for driverless printing (it supports other formats,
> too, but these are formats we cannot generate). Therefore we print in
> PWG Raster format.
>
> It is possible that some printers have firmware bugs, not able to print
> certain files in standard format. It is less probable that the PWG
> Raster provided by us has problems as otherwise I would have received
> many more bug reports.
>
> Now I need also CUPS error_log output from jobs which succeeded for you
> and also I need the files which you have actually sent, both succeeding
> and failing files. Could you attach these?
>
-- 
Jan Mathisen
Email:  jbmi...@gmail.com
Adress: Bispeveien 54B, NO-1362 Hosle
Phone:  +47 97460585
Web:100yr.no


** Attachment added: "IMG_4737x.JPG"
   
https://bugs.launchpad.net/bugs/1964095/+attachment/5571377/+files/IMG_4737x.JPG

** Attachment added: "Truloc-211-Retainer.pdf"
   
https://bugs.launchpad.net/bugs/1964095/+attachment/5571378/+files/Truloc-211-Retainer.pdf

** Attachment added: "error_log"
   https://bugs.launchpad.net/bugs/1964095/+attachment/5571379/+files/error_log

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

Title:
  print sent to Epson ET-2810 is not printed

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is a new network printer in my home/local network.  It works ok from my 
mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my 
preferred system.  I can print the test page consistently via 'Settings - 
Printers - Printer Details'; occasionally I have managed to print a simple text 
e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process 
shows the job entering the print queue and being completed, but nothing appears 
to happen on the printer.
  I have used 'ubuntu-bug cups'to generate this report, so I hope it has 
included all the info you need, but please let me know if I can provide 
anything you are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 10:11:02 2022
  InstallationDate: Installed on 2021-03-13 (359 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/
  MachineType: Dell Inc. XPS 8700
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8700
  dmi.product.sku: XPS 8700
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed

[Jan Mathisen]

OK, that worked; file attached.

On 2022-03-21 17:26, Till Kamppeter wrote:
> Seems that your version of "driverless" is too old, not yet having the "
> --std-ipp-uris" option (see also output of "driverless -h").
>
> But I have found the URI you need in your error_log. Please run the
> following command:
>
> ipptool -tv ipp://EPSON0EF3E0.local:631/ipp/print get-printer-
> attributes.test > attrs.txt
>
> and attach attrs.txt.
>
-- 
Jan Mathisen
Email:  jbmi...@gmail.com
Adress: Bispeveien 54B, NO-1362 Hosle
Phone:  +47 97460585
Web:100yr.no


** Attachment added: "attrs.txt"
   https://bugs.launchpad.net/bugs/1964095/+attachment/5571360/+files/attrs.txt

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

Title:
  print sent to Epson ET-2810 is not printed

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is a new network printer in my home/local network.  It works ok from my 
mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my 
preferred system.  I can print the test page consistently via 'Settings - 
Printers - Printer Details'; occasionally I have managed to print a simple text 
e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process 
shows the job entering the print queue and being completed, but nothing appears 
to happen on the printer.
  I have used 'ubuntu-bug cups'to generate this report, so I hope it has 
included all the info you need, but please let me know if I can provide 
anything you are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 10:11:02 2022
  InstallationDate: Installed on 2021-03-13 (359 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/
  MachineType: Dell Inc. XPS 8700
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8700
  dmi.product.sku: XPS 8700
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions

[Joe Barnett]

I do occasionally get crashes when attempting to rearrange tabs as well.
The crashes happen both in .deb & snap versions of firefox though?

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

Title:
  Cannot rearrange Firefox (snap) browser tabs in Wayland sessions

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+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 1964095] Re: print sent to Epson ET-2810 is not printed

[Till Kamppeter]

I your error_log I have found the following:

D [21/Mar/2022:15:08:48 +0100] [Job 312] Send-Document: client-error-
document-format-error (client-error-document-format-error)

This looks like that the printer was not able to work with the data it
received.

The printer reports that it accepts PWG Raster as the only of the known
data formats used for driverless printing (it supports other formats,
too, but these are formats we cannot generate). Therefore we print in
PWG Raster format.

It is possible that some printers have firmware bugs, not able to print
certain files in standard format. It is less probable that the PWG
Raster provided by us has problems as otherwise I would have received
many more bug reports.

Now I need also CUPS error_log output from jobs which succeeded for you
and also I need the files which you have actually sent, both succeeding
and failing files. Could you attach these?

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

Title:
  print sent to Epson ET-2810 is not printed

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is a new network printer in my home/local network.  It works ok from my 
mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my 
preferred system.  I can print the test page consistently via 'Settings - 
Printers - Printer Details'; occasionally I have managed to print a simple text 
e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process 
shows the job entering the print queue and being completed, but nothing appears 
to happen on the printer.
  I have used 'ubuntu-bug cups'to generate this report, so I hope it has 
included all the info you need, but please let me know if I can provide 
anything you are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 10:11:02 2022
  InstallationDate: Installed on 2021-03-13 (359 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/
  MachineType: Dell Inc. XPS 8700
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8700
  dmi.product.sku: XPS 8700
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed

[Till Kamppeter]

Seems that your version of "driverless" is too old, not yet having the "
--std-ipp-uris" option (see also output of "driverless -h").

But I have found the URI you need in your error_log. Please run the
following command:

ipptool -tv ipp://EPSON0EF3E0.local:631/ipp/print get-printer-
attributes.test > attrs.txt

and attach attrs.txt.

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

Title:
  print sent to Epson ET-2810 is not printed

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is a new network printer in my home/local network.  It works ok from my 
mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my 
preferred system.  I can print the test page consistently via 'Settings - 
Printers - Printer Details'; occasionally I have managed to print a simple text 
e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process 
shows the job entering the print queue and being completed, but nothing appears 
to happen on the printer.
  I have used 'ubuntu-bug cups'to generate this report, so I hope it has 
included all the info you need, but please let me know if I can provide 
anything you are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 10:11:02 2022
  InstallationDate: Installed on 2021-03-13 (359 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/
  MachineType: Dell Inc. XPS 8700
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8700
  dmi.product.sku: XPS 8700
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed

[Jan Mathisen]

Tried the below, but it didn't work for me:

jbm@curlew:~$ driverless --std-ipp-uris
ERROR: Unable to create PPD file: Could not poll sufficient capability 
info from the printer (--std-ipp-uris, (null)) via IPP!


On 2022-03-21 15:36, Till Kamppeter wrote:
> Thanks for the files.
>
> For the "ipptool -tv ..." command do the following:
>
> Run
>
> driverless --std-ipp-uris
>
> You get an URI for your printer in standard IPP format. Please use that
> URI for the "ipptool -tv ..." command of my comment above (comment #2)
> and attach the attrs.txt here.
>
-- 
Jan Mathisen
Email:  jbmi...@gmail.com
Adress: Bispeveien 54B, NO-1362 Hosle
Phone:  +47 97460585
Web:100yr.no

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

Title:
  print sent to Epson ET-2810 is not printed

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is a new network printer in my home/local network.  It works ok from my 
mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my 
preferred system.  I can print the test page consistently via 'Settings - 
Printers - Printer Details'; occasionally I have managed to print a simple text 
e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process 
shows the job entering the print queue and being completed, but nothing appears 
to happen on the printer.
  I have used 'ubuntu-bug cups'to generate this report, so I hope it has 
included all the info you need, but please let me know if I can provide 
anything you are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 10:11:02 2022
  InstallationDate: Installed on 2021-03-13 (359 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/
  MachineType: Dell Inc. XPS 8700
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8700
  dmi.product.sku: XPS 8700
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1965673] Re: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management

[Launchpad Bug Tracker]

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

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

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

Title:
  Object 0x... of type IBusText has been finalized while it was still
  owned by gjs, this is due to invalid memory management

Status in ibus:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 development branch @ 20/03/2022

  Journal logs spam a lot of lines like these:

  mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x7f896cf7cad0 of type 
IBusText has been finalized while it was still owned by gjs, this is due to 
invalid memory management. 
  mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x557a992efd20 of type 
IBusText has been finalized while it was still owned by gjs, this is due to 
invalid memory management

  
  Probably regression bug upstream: 

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

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 13:34:37 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1965673/+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 1936907] Re: [MIR] ADSys

[Didier Roche]

$ ./change-override -c main -B adsys
Override component to main
adsys 0.8.2 in jammy: universe/admin -> main
adsys 0.8.2 in jammy amd64: universe/admin/optional/100% -> main
adsys 0.8.2 in jammy arm64: universe/admin/optional/100% -> main
adsys 0.8.2 in jammy armhf: universe/admin/optional/100% -> main
adsys 0.8.2 in jammy ppc64el: universe/admin/optional/100% -> main
adsys 0.8.2 in jammy riscv64: universe/admin/optional/100% -> main
adsys 0.8.2 in jammy s390x: universe/admin/optional/100% -> main
Override [y|N]? y
7 publications overridden.

** Changed in: adsys (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [MIR] ADSys

Status in adsys package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  Available on all archs, available starting hirsute. It will be
  backported to Focal once an FFe has been accepted.

  [Rationale]

  We are supporting GPO Active Directory support on ubuntu starting
  hirsute. This features allows for an administrator to configure their
  Active Directory server to deploy per-machine and per-user
  configurations, enforce rules and other domain policies.

  Right now, dconf keys, sudo administration rights and computer and
  user scripts are supported.

  This feature is built and use the krb5 tickets which are provided by SSSD. 
Basically:
  - SSSD is dealing with user and machine registration/authentification and 
enforce password policies
  - ADSys is handling GPO enforcement and support. The Ubuntu specific policies 
needs to be installed on the Active Directory server (they are contained in the 
daemon).

  [Security]

  The daemon is started is running as a root user to be able to enforce
  machine policies, like rebuilding dconf databases, setting profiles.
  User only interacts with the client side (both sides communicates over
  GRPC), which can be ran as any user.

  Polkit is used to restrain access to some part of the API.

  There is a PAM module to build on demand per-user policy once
  authenticated with SSSD. They are rejected if the authentication or
  not all affected policies could be downloaded.

  [Quality assurance]

  Joining a domain in the ubiquity desktop installer makes the machine
  joining the AD domain and install adsys functionality. The package
  will be seeded directly on the desktop ISO.

  An extensive testsuite (more than 1k) is included and available as
  autopkgtests for rdepends. The whole stack is tested (even the
  client/daemon interaction) and coverage is measured (including in the
  small python script). However, tests with a real Active Directory
  server can only be done manually as there is no setup available in the
  autopkgtests infrastructure.

  [Dependencies]

  Main dependencies are libsmbclient, python3 (an embeeded script
  allows, via samba, connecting to AD LDAP) and SSSD/KRB5.

  This is a Go package, and all dependencies are vendored, and versions
  are controlled via go.mod. We are using dependabot (from Github) to
  automatically get notified of any dependencies updates (and security
  issues), which opens a PR, rebuild and run all tests to report it
  there. We are thus able to quickly merge them.

  [Standards compliance]

  Standard debhelper packaging, including a systemd service.

  [Maintenance]

  The desktop team will maintain it.

  * we commit to test no-change-rebuilds triggered by a dependent 
library/compiler and to fix any issues found for the lifetime of the release 
(including ESM when included)
  * we will provide timely testing of no-change-rebuilds from the security 
team, fixing the rebuilt package as necessary
  * we commit to  provide updates to the security team for any affected 
vendored code for the lifetime of the release (including ESM when included)
  * we will provide timely, high quality updates for the security team to 
sponsor to fix issues in the affected vendored code

  [Background information]

  ADSys is composed of:
  - a daemon, named adsysd, running as root. This one will shutdown after a 
period of inactivity without any active request. It is socket activated.
  - a client, named adsysctl (which is a symlink to adsysd and only differ 
behavior from its executable name), which is running as the user (or root on 
boot for machine update). This ones optionally wakes up adsysd, connect through 
an Unix socket with SO_PEERCRED to communicate current user running the 
process. We are using grpc to communicate between the client and service.

  Each client request is validated through polkit, matching user name
  and permissions. The daemon will reject any unauthorized client
  connections. Note that all actions are always performed from executing
  the client, even the scheduled one by a cron.

  The daemon contains a python embedded script that uses samba utilities
  to connect with GSSAPI to 

[Desktop-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed

[Till Kamppeter]

Thanks for the files.

For the "ipptool -tv ..." command do the following:

Run

driverless --std-ipp-uris

You get an URI for your printer in standard IPP format. Please use that
URI for the "ipptool -tv ..." command of my comment above (comment #2)
and attach the attrs.txt here.

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

Title:
  print sent to Epson ET-2810 is not printed

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is a new network printer in my home/local network.  It works ok from my 
mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my 
preferred system.  I can print the test page consistently via 'Settings - 
Printers - Printer Details'; occasionally I have managed to print a simple text 
e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process 
shows the job entering the print queue and being completed, but nothing appears 
to happen on the printer.
  I have used 'ubuntu-bug cups'to generate this report, so I hope it has 
included all the info you need, but please let me know if I can provide 
anything you are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 10:11:02 2022
  InstallationDate: Installed on 2021-03-13 (359 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/
  MachineType: Dell Inc. XPS 8700
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8700
  dmi.product.sku: XPS 8700
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed

[Till Kamppeter]

Also note that the web interface of Launchpad only allows one attached
file per comment. If you want to attach more files, simply post more
comments, where the actual comment field can also stay empty in case you
wrote everything already in the comment of the first file.

e-mail answers seem to allow any number of attachments though.

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

Title:
  print sent to Epson ET-2810 is not printed

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is a new network printer in my home/local network.  It works ok from my 
mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my 
preferred system.  I can print the test page consistently via 'Settings - 
Printers - Printer Details'; occasionally I have managed to print a simple text 
e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process 
shows the job entering the print queue and being completed, but nothing appears 
to happen on the printer.
  I have used 'ubuntu-bug cups'to generate this report, so I hope it has 
included all the info you need, but please let me know if I can provide 
anything you are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 10:11:02 2022
  InstallationDate: Installed on 2021-03-13 (359 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/
  MachineType: Dell Inc. XPS 8700
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8700
  dmi.product.sku: XPS 8700
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed

[Jan Mathisen]

Hi Till Kamppeter.

Thanks for looking into my bug report.  I have replied via Launchpad, 
but wasn't able to confirm that I managed to attach the files you asked 
for, so I attach them here, too.

--jan


On 2022-03-20 17:54, Till Kamppeter wrote:
> Could you also attach your file
>
> /etc/cups/ppd/EPSON_ET_2810_Series.ppd
>
-- 
Jan Mathisen
Email:  jbmi...@gmail.com
Adress: Bispeveien 54B, NO-1362 Hosle
Phone:  +47 97460585
Web:100yr.no


** Attachment added: "error_log"
   https://bugs.launchpad.net/bugs/1964095/+attachment/5571317/+files/error_log

** Attachment added: "jbm-2810.ppd"
   
https://bugs.launchpad.net/bugs/1964095/+attachment/5571318/+files/jbm-2810.ppd

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

Title:
  print sent to Epson ET-2810 is not printed

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is a new network printer in my home/local network.  It works ok from my 
mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my 
preferred system.  I can print the test page consistently via 'Settings - 
Printers - Printer Details'; occasionally I have managed to print a simple text 
e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process 
shows the job entering the print queue and being completed, but nothing appears 
to happen on the printer.
  I have used 'ubuntu-bug cups'to generate this report, so I hope it has 
included all the info you need, but please let me know if I can provide 
anything you are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 10:11:02 2022
  InstallationDate: Installed on 2021-03-13 (359 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/
  MachineType: Dell Inc. XPS 8700
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8700
  dmi.product.sku: XPS 8700
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed

[Jan Mathisen]

In response to advice 2022_03_20:

jbm@curlew:~/Desktop$ driverless
ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/

jbm@curlew:~/Desktop$ ipptool -tv 
ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ get-printer-attributes.test   > 
attrs.test
ipptool: Unable to connect to "EPSON ET-2810 Series._ipp._tcp.local" on port 
631 - Name or service not known

I suppose this might possibly have failed because I have assigned a new name to 
the printer after the debug report using:
lpadmin -p jbm-2810 -v ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ - E -m 
driverless:ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/
Since then I have had good experience printing pdf- and jpg-files from a 
terminal window using the lp command; printing e-mail and pdf-attachments from 
Thunderbird also works; printing pdf-files from Document Viewer and jpg-files 
from Image Viewer fails.

jbm@curlew:~/Desktop$ cupsctl --debug-logging
Attepted to print a file called "Truloc-211-Retainer.pdf" from Document Viewer 
to jbm-2810; it appears to be placed in the print queue and toleave the print 
queue but no print emerges from the printer. 
I have tried to attach the cups/error_log file 
and the jbm-2810.ppd file.

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

Title:
  print sent to Epson ET-2810 is not printed

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  This is a new network printer in my home/local network.  It works ok from my 
mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my 
preferred system.  I can print the test page consistently via 'Settings - 
Printers - Printer Details'; occasionally I have managed to print a simple text 
e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process 
shows the job entering the print queue and being completed, but nothing appears 
to happen on the printer.
  I have used 'ubuntu-bug cups'to generate this report, so I hope it has 
included all the info you need, but please let me know if I can provide 
anything you are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 10:11:02 2022
  InstallationDate: Installed on 2021-03-13 (359 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/
  MachineType: Dell Inc. XPS 8700
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0KWVT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8700
  dmi.product.sku: XPS 8700
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1965763] Re: night light sunset to sunrise still uses manual settings

[Launchpad Bug Tracker]

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

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

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

Title:
  night light sunset to sunrise still uses manual settings

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  may be related to 1686895

  this has to be done before sunset.

  if you're using night light and you move the setting to manual, and
  then move the start time to before the time is now, you will see night
  light turned on.  then go back to the sunset to sunrise setting, the
  night light will still be on because it's using the manual settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu8
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 09:38:51 2022
  InstallationDate: Installed on 2022-03-05 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965763/+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 1965763] [NEW] night light sunset to sunrise still uses manual settings

[Richard Schneiderman]

Public bug reported:

may be related to 1686895

this has to be done before sunset.

if you're using night light and you move the setting to manual, and then
move the start time to before the time is now, you will see night light
turned on.  then go back to the sunset to sunrise setting, the night
light will still be on because it's using the manual settings.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.4-1ubuntu8
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 21 09:38:51 2022
InstallationDate: Installed on 2022-03-05 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  night light sunset to sunrise still uses manual settings

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  may be related to 1686895

  this has to be done before sunset.

  if you're using night light and you move the setting to manual, and
  then move the start time to before the time is now, you will see night
  light turned on.  then go back to the sunset to sunrise setting, the
  night light will still be on because it's using the manual settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu8
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 09:38:51 2022
  InstallationDate: Installed on 2022-03-05 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965763/+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 1965757] [NEW] Dark theme, text is not visible on axis due to similar color of background in Power Statistics app

[Vidvranjek]

Public bug reported:

When using a dark theme the data in the Power Statistics is barely
visible because text color and background color are almost the same.

Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
Application: gnome-power-statistics


To reproduce:

- Switch to dark theme in Ubuntu appearance settings.
- Open 'Power Statistics' app
- Select 'Laptop battery'
- Select 'History' tab
- Text on both axes is not visible

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-power-manager 3.32.0-2build1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 21 13:49:14 2022
ExecutablePath: /usr/bin/gnome-power-statistics
InstallationDate: Installed on 2022-03-21 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Dark theme, text is not visible on axis due to similar color of
  background in Power Statistics app

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  When using a dark theme the data in the Power Statistics is barely
  visible because text color and background color are almost the same.

  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Application: gnome-power-statistics

  
  To reproduce:

  - Switch to dark theme in Ubuntu appearance settings.
  - Open 'Power Statistics' app
  - Select 'Laptop battery'
  - Select 'History' tab
  - Text on both axes is not visible

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-power-manager 3.32.0-2build1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 13:49:14 2022
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2022-03-21 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1965757/+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 1965449] Re: New Ubuntu logo's white rectangle has too much contrast with the black background of the boot screen

[Launchpad Bug Tracker]

This bug was fixed in the package plymouth - 0.9.5+git20211018-1ubuntu3

---
plymouth (0.9.5+git20211018-1ubuntu3) jammy; urgency=medium

  * themes/ubuntu-logo/ubuntu-logo.png:
- use the right variant of the logo with a dark background instead of
  a white one (lp: #1965449)

 -- Sebastien Bacher   Fri, 18 Mar 2022 11:45:18
+0100

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

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

Title:
  New Ubuntu logo's white rectangle has too much contrast with the black
  background of the boot screen

Status in plymouth package in Ubuntu:
  Fix Released

Bug description:
  0.9.5+git20211018-1ubuntu2

  introduces the new Ubuntu branding logo.
  The white rectangle supporting the new Ubuntu dotted circle does not look 
good to me.
  Too much contrast with the black background.

  Not a big deal and for sure just my opinion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1965449/+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 1712223] Re: open-vm-tools does not work under wayland

[Paride Legovini]

Hello Alexander, note that Xorg is available in Jammy both as the native
graphical session and via xwayland. On this bug report: could you please
elaborate more on what exactly happens? In particular could you guide us
into reproducing the problem on a clean Jammy install, making clear
"what should happen" and "what actually happens" when facing the
problem?

As we're waiting for more information here I'm marking this bug report
as Incomplete.

Thanks!

** Changed in: open-vm-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  open-vm-tools does not work under wayland

Status in open-vm-tools package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  New

Bug description:
  At first I thought this bug was caused with the recent changes in
  open-vm-tools 10.1.10; however, after restoring my VM to the snapshot
  that had 17.04 and re-performing the dist-upgrade with open-vm-tools
  and open-vm-tools-desktop held at 10.1.5 I am experiencing the same
  issue where VMWare Workstation no longer can interact with display
  resolution detection of the host monitor(s). Multiple monitor support
  is also lost in the update process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 17:09:59 2017
  DistUpgraded: 2017-08-07 09:05:02,559 DEBUG found components: 
{'artful-updates': {'multiverse', 'restricted', 'universe', 'main'}, 'artful': 
{'multiverse', 'restricted', 'universe', 'main'}, 'artful-security': 
{'multiverse', 'restricted', 'universe', 'main'}}
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.26, 4.10.0-30-generic, x86_64: installed
   virtualbox, 5.1.26, 4.12.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2016-11-30 (264 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-08-07 (14 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 21 16:27:55 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputVirtualPS/2 VMware VMMouse MOUSE, id 8
   inputVirtualPS/2 VMware VMMouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 

[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions

[Olivier Tilloy]

This appears to be a snap-specific problem, indeed.

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

Title:
  Cannot rearrange Firefox (snap) browser tabs in Wayland sessions

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+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 1712223] Re: open-vm-tools does not work under wayland

[Christian Ehrhardt ]

Thanks for the ping on this old case Alexander!

Can you confirm that this is what you see on 22.04 with the there recent
2:11.3.5-1ubuntu4 version of open-vm-tools?

I have subscribed John Wolfe who looks after open-vm-tools from VMwares
side and might have more details.

Further I added a bug task for "wayland" so that the Desktop team can
have a look as well.

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

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

Title:
  open-vm-tools does not work under wayland

Status in open-vm-tools package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  New

Bug description:
  At first I thought this bug was caused with the recent changes in
  open-vm-tools 10.1.10; however, after restoring my VM to the snapshot
  that had 17.04 and re-performing the dist-upgrade with open-vm-tools
  and open-vm-tools-desktop held at 10.1.5 I am experiencing the same
  issue where VMWare Workstation no longer can interact with display
  resolution detection of the host monitor(s). Multiple monitor support
  is also lost in the update process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 17:09:59 2017
  DistUpgraded: 2017-08-07 09:05:02,559 DEBUG found components: 
{'artful-updates': {'multiverse', 'restricted', 'universe', 'main'}, 'artful': 
{'multiverse', 'restricted', 'universe', 'main'}, 'artful-security': 
{'multiverse', 'restricted', 'universe', 'main'}}
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.26, 4.10.0-30-generic, x86_64: installed
   virtualbox, 5.1.26, 4.12.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2016-11-30 (264 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-08-07 (14 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 21 16:27:55 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputVirtualPS/2 VMware VMMouse MOUSE, id 8
   inputVirtualPS/2 VMware VMMouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: vmware

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1962021] Re: Make the deb package install the firefox snap

[Launchpad Bug Tracker]

This bug was fixed in the package firefox - 1:1snap1-0ubuntu1

---
firefox (1:1snap1-0ubuntu1) jammy; urgency=medium

  * Install the firefox snap in place of the debian packages (LP:
#1962021)

 -- Olivier Tilloy   Tue, 22 Feb 2022
10:47:48 +0100

** Changed in: firefox (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Make the deb package install the firefox snap

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Canonical and Mozilla are working together to make the firefox snap
  the only supported package in Ubuntu, thus deprecating the deb package
  in the archive.

  This bug tracks the transformation of the firefox package in the
  archive into a transitional package that installs the snap, much like
  was done for chromium-browser in Ubuntu 19.10.

  There are a number of known problems and regressions with the snap
  compared to the deb (see
  https://bugzilla.mozilla.org/show_bug.cgi?id=snap and
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap),
  those are actively being worked on and will be addressed in due time,
  please refrain from using this bug to point them out. Instead, file
  separate bugs in the upstream bug tracker
  (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify
  this is about the snap package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+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 1965750] [NEW] [jammy regression] No sound from onboard audio (playback / record)

[Luis Alberto Pabón]

Public bug reported:

After updates I applied last friday, my onboard audio has ceased to
function. No audio comes out the laptop speakers and no audio goes in
the internal microphone (built in audio).

If I connect my bluetooth headset (Bose NC700) the audio works, but only
ever in mono. I cannot switch to the A2DP sink, it stays on HPF mono.

I tried switching from pulseaudio to pipewire and pipewire-pulse, and I
kind of made it work - the bluetooth headset works correctly, and the
onboard audio works again after switching default inputs and outputs a
number of times.

I just want to stress my laptop's audio has worked fine for years in all
versions of ubuntu including Jammy, but only up until Friday Jan the
18th 2022.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Mar 21 11:48:25 2022
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  [jammy regression] No sound from onboard audio (playback / record)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After updates I applied last friday, my onboard audio has ceased to
  function. No audio comes out the laptop speakers and no audio goes in
  the internal microphone (built in audio).

  If I connect my bluetooth headset (Bose NC700) the audio works, but
  only ever in mono. I cannot switch to the A2DP sink, it stays on HPF
  mono.

  I tried switching from pulseaudio to pipewire and pipewire-pulse, and
  I kind of made it work - the bluetooth headset works correctly, and
  the onboard audio works again after switching default inputs and
  outputs a number of times.

  I just want to stress my laptop's audio has worked fine for years in
  all versions of ubuntu including Jammy, but only up until Friday Jan
  the 18th 2022.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Mon Mar 21 11:48:25 2022
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago)
  dmi.bios.date: 11/17/2019
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750/+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 1844453]

[Mikekaganski]

@cloph: could we possibly use some Python library (
https://oauth.net/code/python/ ), like we use smtplib in our
scripting/source/pyprov/mailmerge.py, which implements
com::sun::star::mail::XMailServiceProvider etc?

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

Title:
  [upstream] Access to the Google remote account does not work

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

Bug description:
  I have a Google account with 2FA login, from LibreOffice I try to add the 
remote account, but it doesn't work, it asks me for a 6-digit PIN.
  Investigating to see if it was just my problem, I discovered that this is a 
long-standing LibreOffice bug (1) and seems unresolved.

  The last report confirms this: "2019-07-04 04:44:41 UTC
  This feature doesn't work with my Google account _w/o_
  2FA.

  Bug hasn't be resolved for about 3 years and "very soon"
  we may celebrate 5 years anniversary.  %-("

  1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 17 23:00:10 2019
  InstallationDate: Installed on 2019-02-18 (210 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  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/1844453/+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 1965105] Re: application crashes since update

[Amnon Yekutieli]

Crashed again today.

Need to reboot computer... (logout + login not enough).

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

Title:
  application crashes since update

Status in libreoffice package in Ubuntu:
  New

Bug description:
  
  Since a few days ago the program LibreOffice Writer is broken.

  1) Does not launch, or launches after several clicks a long (> 2 min)
  dely.

  2) When open, the program often freezes and needs to be killed.

  My system:

  Operating System: Kubuntu 21.10
  KDE Plasma Version: 5.24.3
  KDE Frameworks Version: 5.91.0
  Qt Version: 5.15.2
  Kernel Version: 5.13.0-35-generic (64-bit)
  Graphics Platform: X11
  Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz
  Memory: 15.3 GiB of RAM
  Graphics Processor: Mesa Intel® Xe Graphics

  
  Using Hebrew.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libreoffice-writer 1:7.2.5-0ubuntu0.21.10.3
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Mar 16 11:19:12 2022
  InstallationDate: Installed on 2021-06-15 (273 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to impish on 2022-01-12 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1965105/+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 1965639] Re: purple screen after login using fingerprint

[Johannes Zeiser]

Here is the file from step 3

The directory /var/crash is empty, or at least ls /var/crash/ does not
return anything.

There are some error reports, but just about onedrive and they are from
last year, so I doubt they are relevant for this problem.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965639/+attachment/5571260/+files/prevboot.txt

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

Title:
  purple screen after login using fingerprint

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I updated the machine yesterday, and additionally added the
  fingerprint to pam using pam-auth-update. The screen now stays purple
  after logging in using the finger, but works fine after logging in
  using the password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 19 21:37:43 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.103.01, 5.13.0-28-generic, x86_64: installed
   nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2294]
  InstallationDate: Installed on 2020-12-10 (464 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20NN002NGE
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=2bcb2bd8-2364-4f28-9085-f6c366d45c6d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2021
  dmi.bios.release: 1.89
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2LET89W (1.89 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NN002NGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2LET89W(1.89):bd11/24/2021:br1.89:efr1.20:svnLENOVO:pn20NN002NGE:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20NN_BU_Think_FM_ThinkPadX390Yoga:
  dmi.product.family: ThinkPad X390 Yoga
  dmi.product.name: 20NN002NGE
  dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga
  dmi.product.version: ThinkPad X390 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965639/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/417157

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/417158

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

[Dave Jones]

Sorry, this slipped off my radar -- I'll get on with the required PRs
today

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

[Sebastian Heiden]

** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+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/gnome-shell/+bug/1876632/+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 1965740] [NEW] BlueZ 5.64 release

[Daniel van Vugt]

Public bug reported:

http://www.bluez.org/release-of-bluez-5-64/

At least for 22.10, but maybe for 22.04 too.

** Affects: bluez (Ubuntu)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: Triaged


** Tags: needs-packaging

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

Title:
  BlueZ 5.64 release

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  http://www.bluez.org/release-of-bluez-5-64/

  At least for 22.10, but maybe for 22.04 too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1965740/+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 1965501] Re: [snap] Does not follow dark theme

[Olivier Tilloy]

Thanks for the report François.
I'm marking the bug incomplete so that it will auto-expire in 60 days from now 
if it hasn't been updated, which should give plenty of time to follow up.

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

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

Title:
  [snap] Does not follow dark theme

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  (TB snap 91.7.0, Ubuntu Jammy with latest funny color features)

  TB keeps light theme when I switch to dark theme.
  Firefox snap is ok.

  gtk common themes snap: 0.1-65-g4ed9cc8 (candidate)

  System theme is selected in TB prefs, of course.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1965501/+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 1965627] Re: Unlock screen password is barely visible/contrasting

[Daniel van Vugt]

Fixed in https://github.com/ubuntu/yaru/pull/3513

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => Fix Committed

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

** Changed in: yaru-theme (Ubuntu)
 Assignee: (unassigned) => Paul (jupiter007)

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Unlock screen password is barely visible/contrasting

Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  Returning from suspend login screen password field  barely visible.
  see attachment.
  corrado@corrado-p5-jj-0203:~$ inxi -Fx
  System:
Host: corrado-p5-jj-0203 Kernel: 5.15.0-23-generic x86_64 bits: 64
  compiler: gcc v: 11.2.0 Desktop: GNOME 42.beta
  Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:
Type: Desktop Mobo: Gigabyte model: H87M-D3H v: x.x
  serial:  UEFI: American Megatrends v: F3
  date: 04/24/2013
  CPU:
Info: dual core model: Intel Core i3-4130 bits: 64 type: MT MCP
  arch: Haswell rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2195 high: 2196 min/max: 800/3400 cores: 1: 2195
  2: 2195 3: 2195 4: 2196 bogomips: 27136
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
  vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0
Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  gpu: i915 resolution: 1680x1050~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2)
  v: 4.5 Mesa 21.3.5 direct render: Yes
  Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel v: kernel bus-ID: 00:03.0
Device-2: Intel 8 Series/C220 Series High Definition Audio
  vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
Sound Server-1: ALSA v: k5.15.0-23-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Gigabyte driver: r8169 v: kernel port: e000 bus-ID: 02:00.0
IF: enp2s0 state: down mac: 94:de:80:7e:90:a7
Device-2: D-Link DWA-121 802.11n Wireless N 150 Pico Adapter [Realtek
RTL8188CUS]
  type: USB driver: rtl8192cu bus-ID: 3-14:5
IF: wlx48ee0c2322b8 state: up mac: 48:ee:0c:23:22:b8
  Drives:
Local Storage: total: 1.14 TiB used: 11.51 GiB (1.0%)
ID-1: /dev/sda vendor: Crucial model: CT250MX500SSD1 size: 232.89 GiB
ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB
  Partition:
ID-1: / size: 16.21 GiB used: 11.5 GiB (71.0%) fs: ext4 dev: /dev/sda5
ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat
  dev: /dev/sda1
  Swap:
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) dev: /dev/sdb2
  Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
  Info:
Processes: 246 Uptime: 5h 28m Memory: 7.65 GiB used: 2.08 GiB (27.2%)
Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1869 Shell: Bash
v: 5.1.16 inxi: 3.3.13
  corrado@corrado-p5-jj-0203:~$ 

  Note: I'm unsure package is gdm3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 41.3-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 19 17:18:46 2022
  InstallationDate: Installed on 2022-02-08 (39 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1965627/+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 1965666] Re: firefox crashed, unable even to quit

[Amnon Yekutieli]

I just checke. It says "No crash reports have been submitted."

I must say this is a rare event (this crash), but of course it might be
due to a new bug. Will update if it happens once more.

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

Title:
  firefox crashed, unable even to quit

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  
  Firefox crashed, unable even to quit via system monitor. 

  First time today.

  

  Operating System: Kubuntu 21.10
  KDE Plasma Version: 5.24.3
  KDE Frameworks Version: 5.92.0
  Qt Version: 5.15.2
  Kernel Version: 5.13.0-35-generic (64-bit)
  Graphics Platform: X11
  Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz
  Memory: 15.3 GiB of RAM
  Graphics Processor: Mesa Intel® Xe Graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 98.0.1+build2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amyekut1018 F pulseaudio
  BuildID: 20220313140707
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Mar 20 12:53:57 2022
  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:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-06-15 (277 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.100.102.1 dev wlp0s20f3 proto dhcp metric 600 
   10.100.102.0/24 dev wlp0s20f3 proto kernel scope link src 10.100.102.5 
metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  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:364
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=98.0.1/20220313140707 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to impish on 2022-01-12 (66 days ago)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 3.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.5.1
  dmi.board.name: 0DXP1F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.5.1:bd02/25/2022:br3.5:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1965666/+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 1965664] Re: Safer way to build Thunderbird snap

[Olivier Tilloy]

This would require an override-pull scriptlet.

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

** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
   Safer way to build Thunderbird snap

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hello dear Canonical team,

  the offered Thunderbird snap uses only HTTPS to secure the download of 
Thunderbird itself and its language packs. At least I found this snapcraft.yaml 
proving it:
  
https://git.launchpad.net/~desktop-snappers/thunderbird/+git/snap/tree/snapcraft.yaml?h=stable

  Due to recent attacks against HTTPS by changing network routes and
  creating new trusted certificates for official domains [1], HTTPS
  alone is not trustworthy anymore. Could you please integrate a check
  of the SHA512SUMS (an additional GPG check would be the best of course
  but is maybe not so easy to implement) after downloading Thunderbird
  itself and all the language packs? The same is already done for the
  Chromium snap as far as I could see.

  Thank you very much!

  [1] https://medium.com/s2wblog/post-mortem-of-klayswap-incident-
  through-bgp-hijacking-en-3ed7e33de600

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1965664/+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 1965666] Re: firefox crashed, unable even to quit

[Olivier Tilloy]

Can you check whether there's a corresponding entry in about:crashes,
submit it if it hasn't been submitted yet, and share the link to the
crash report here?

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

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

Title:
  firefox crashed, unable even to quit

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  
  Firefox crashed, unable even to quit via system monitor. 

  First time today.

  

  Operating System: Kubuntu 21.10
  KDE Plasma Version: 5.24.3
  KDE Frameworks Version: 5.92.0
  Qt Version: 5.15.2
  Kernel Version: 5.13.0-35-generic (64-bit)
  Graphics Platform: X11
  Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz
  Memory: 15.3 GiB of RAM
  Graphics Processor: Mesa Intel® Xe Graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: firefox 98.0.1+build2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amyekut1018 F pulseaudio
  BuildID: 20220313140707
  CasperMD5CheckResult: pass
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Mar 20 12:53:57 2022
  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:364
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-06-15 (277 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.100.102.1 dev wlp0s20f3 proto dhcp metric 600 
   10.100.102.0/24 dev wlp0s20f3 proto kernel scope link src 10.100.102.5 
metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
  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:364
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=98.0.1/20220313140707 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to impish on 2022-01-12 (66 days ago)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 3.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.5.1
  dmi.board.name: 0DXP1F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.5.1:bd02/25/2022:br3.5:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1965666/+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 1965701] Re: Background image and icons missing after suspend

[Daniel van Vugt]

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

See also https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3583

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

Title:
  Background image and icons missing after suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After resuming the system from suspend the lockscreen image,
  background image and some of the icons are missing.

  This includes most of the ubuntu-dock icons, but also some of the
  gnome shell icons.

  Restarting gdm3 using `sudo service gdm3 restart` resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 00:16:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-23 (25 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1965701/+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 1965701] Re: Background image and icons missing after suspend

[Daniel van Vugt]

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

Bug 1876632 says "missing" in its title because when the GPU memory gets
corrupted that's one of the most common side-effects.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3583
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3583

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

Title:
  Background image and icons missing after suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After resuming the system from suspend the lockscreen image,
  background image and some of the icons are missing.

  This includes most of the ubuntu-dock icons, but also some of the
  gnome shell icons.

  Restarting gdm3 using `sudo service gdm3 restart` resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 00:16:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-23 (25 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1965701/+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 1965701] Re: Background image and icons missing after suspend

[Sebastian Heiden]

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

I've checked out bug #1876632 and it doesn't look like a duplicate bug
to me.

This bug is about missing images and icons, whilst bug #1876632 is about
corrupted icons, which seems like a clear difference to me after
checking the attached screenshots.

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

Title:
  Background image and icons missing after suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After resuming the system from suspend the lockscreen image,
  background image and some of the icons are missing.

  This includes most of the ubuntu-dock icons, but also some of the
  gnome shell icons.

  Restarting gdm3 using `sudo service gdm3 restart` resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 00:16:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-23 (25 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1965701/+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 1965072] Re: In Xorg sessions, desktop icons flicker when entering the overview

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

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

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

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

Title:
  In Xorg sessions, desktop icons flicker when entering the overview

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Invalid

Bug description:
  In Xorg sessions, desktop icons flicker when entering the overview.

  I think this is a combination of a new feature in DING:

https://gitlab.com/rastersoft/desktop-icons-
  ng/-/commit/6ab838e832b3771

  and an old problem where desktop icon fading is only implemented for
  Xorg sessions, as shown in:

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1395
(see also https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1070)

  If DING intends to make the icons vanish immediately then also fading
  them in Xorg sessions may be causing them to disappear and then
  reappear to fade out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-desktop-icons-ng 39-2ubuntu1 [modified: 
usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 10:29:21 2022
  InstallationDate: Installed on 2021-11-05 (130 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons-ng
  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/1965072/+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 1964496] Re: [GS 42] display switching key does not work

[Daniel van Vugt]

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

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

** Tags removed: fixed-upstream rls-jj-incoming upstream
** Tags added: fixed-upstreamupstream

** Changed in: gnome-shell (Ubuntu)
   Importance: High => Low

** Tags removed: fixed-upstreamupstream
** Tags added: fixed-upstream upstream

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

Title:
  [GS 42] display switching key does not work

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

Bug description:
  Hi,

  Using GS 42 in Jammy, when I press the display switch key of my laptop 
keyboard, I get the usual pop-up but the selected item is not applied.
  I have to use gnome-control-center to configure my displays. (gcc is slow to 
start these days?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1964496/+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 1965657] Re: Ubuntu 20.04 loses monitor resolution after waking from sleep

[Daniel van Vugt]

Thanks for the bug report.

Please clarify:

 * which monitor you mean
 * what is the expected resolution?
 * what resolution do you see instead?

Also the current/preferred information in Xrandr.txt seems to be
incomplete so please run:

  xrandr > xrandr2.txt

when the resolution is WRONG, and attach the resulting text file here.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  Ubuntu 20.04 loses monitor resolution after waking from sleep

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 loses monitor resolution after waking from sleep

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Mar 20 13:39:08 2022
  DistUpgraded: 2022-02-08 01:01:24,407 DEBUG running apport_crash()
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.32, 5.13.0-30-generic, x86_64: installed
   virtualbox, 6.1.32, 5.13.0-35-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Haswell-ULT Integrated Graphics Controller 
[8086:0a16]
  InstallationDate: Installed on 2021-04-27 (326 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  LightdmDisplayLog:
   (EE) event5  - SEMICO   USB Gaming Keyboard : client bug: event processing 
lagging behind by 28ms, your system is too slow
   (EE) event5  - SEMICO   USB Gaming Keyboard : client bug: event processing 
lagging behind by 13ms, your system is too slow
   (EE) event5  - SEMICO   USB Gaming Keyboard : WARNING: log rate limit 
exceeded (5 msgs per 60min). Discarding future messages.
   (EE) event4  - USB OPTICAL MOUSE : client bug: event processing lagging 
behind by 11ms, your system is too slow
   (EE) event4  - USB OPTICAL MOUSE : client bug: event processing lagging 
behind by 14ms, your system is too slow
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=40d7f55a-4639-417b-ac6b-41fd4a9d344b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2022-02-07 (40 days ago)
  dmi.bios.date: 01/29/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd01/29/2015:br5.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnCRESCENTBAY:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1965657/+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 1965627] Re: Unlock screen password is barely visible/contrasting

[Daniel van Vugt]

** Tags added: visual-quality

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

Title:
  Unlock screen password is barely visible/contrasting

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  Returning from suspend login screen password field  barely visible.
  see attachment.
  corrado@corrado-p5-jj-0203:~$ inxi -Fx
  System:
Host: corrado-p5-jj-0203 Kernel: 5.15.0-23-generic x86_64 bits: 64
  compiler: gcc v: 11.2.0 Desktop: GNOME 42.beta
  Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:
Type: Desktop Mobo: Gigabyte model: H87M-D3H v: x.x
  serial:  UEFI: American Megatrends v: F3
  date: 04/24/2013
  CPU:
Info: dual core model: Intel Core i3-4130 bits: 64 type: MT MCP
  arch: Haswell rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2195 high: 2196 min/max: 800/3400 cores: 1: 2195
  2: 2195 3: 2195 4: 2196 bogomips: 27136
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
  vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0
Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  gpu: i915 resolution: 1680x1050~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2)
  v: 4.5 Mesa 21.3.5 direct render: Yes
  Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel v: kernel bus-ID: 00:03.0
Device-2: Intel 8 Series/C220 Series High Definition Audio
  vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
Sound Server-1: ALSA v: k5.15.0-23-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Gigabyte driver: r8169 v: kernel port: e000 bus-ID: 02:00.0
IF: enp2s0 state: down mac: 94:de:80:7e:90:a7
Device-2: D-Link DWA-121 802.11n Wireless N 150 Pico Adapter [Realtek
RTL8188CUS]
  type: USB driver: rtl8192cu bus-ID: 3-14:5
IF: wlx48ee0c2322b8 state: up mac: 48:ee:0c:23:22:b8
  Drives:
Local Storage: total: 1.14 TiB used: 11.51 GiB (1.0%)
ID-1: /dev/sda vendor: Crucial model: CT250MX500SSD1 size: 232.89 GiB
ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB
  Partition:
ID-1: / size: 16.21 GiB used: 11.5 GiB (71.0%) fs: ext4 dev: /dev/sda5
ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat
  dev: /dev/sda1
  Swap:
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) dev: /dev/sdb2
  Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
  Info:
Processes: 246 Uptime: 5h 28m Memory: 7.65 GiB used: 2.08 GiB (27.2%)
Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1869 Shell: Bash
v: 5.1.16 inxi: 3.3.13
  corrado@corrado-p5-jj-0203:~$ 

  Note: I'm unsure package is gdm3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 41.3-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 19 17:18:46 2022
  InstallationDate: Installed on 2022-02-08 (39 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  SourcePackage: gdm3
  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/1965627/+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 1964496] Re: [GS 42] display switching key does not work

[Francois Thirioux]

Solved upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5217

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

Title:
  [GS 42] display switching key does not work

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Hi,

  Using GS 42 in Jammy, when I press the display switch key of my laptop 
keyboard, I get the usual pop-up but the selected item is not applied.
  I have to use gnome-control-center to configure my displays. (gcc is slow to 
start these days?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1964496/+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 1965648] Re: Autorotate initiates, but doesn't reset

[Daniel van Vugt]

Please try logging into 'Ubuntu on Xorg' and tell us if the same bug
occurs. I'm reminded of bug 1960747.

Please also run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

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

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

Title:
  Autorotate initiates, but doesn't reset

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  In jammy I can get mutter's auto-rotate to switch to portrait mode
  ("right-up") by rotating the device (this only worked in impish if I
  installed the autorotate gnome-shell extension).

  However, putting it back into "normal" orientation doesn't put the
  screen back in landscape mode.  Flipping it around ("left-up") does
  swap to the reverse portrait mode, but still can't get back to
  "normal" afterward.

  running `monitor-sensor` does show the accelerometer orientation
  change events (including the "normal" ones) triggering properly, just
  the desktop doesn't respond.

  Plugging in an external monitor does seem to trigger the desktop to go
  back to normal landscape mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Mar 19 15:41:42 2022
  InstallationDate: Installed on 2019-08-17 (945 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+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 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell

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

Title:
  42beta: moving mouse as screen is fading to screensaver prevents input
  to shell

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  If you move the mouse as the system fades into black for the
  screensaver, the screensaver will be prevented as normal, but the user
  will not be able to interact with the shell.

  Mouse clicks are ignored, and most key presses are ignored too.

  Workaround is to press super to enter shell overview, then super again
  to close, and mouse clicks will begin working again.

  gnome-shell 42~beta-1ubuntu2 from -proposed.

  [Testcase]

  1) Leave your system idle, until the screen starts fading to black
  2) As the screen is fading to black, move the mouse to prevent screensaver.
  3) Attempt to click any window or type something

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+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 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell

[Daniel van Vugt]

I'm starting to think this might be related to bug 1965085. Although
pressing Tab works there, but doesn't work here.

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

Title:
  42beta: moving mouse as screen is fading to screensaver prevents input
  to shell

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  If you move the mouse as the system fades into black for the
  screensaver, the screensaver will be prevented as normal, but the user
  will not be able to interact with the shell.

  Mouse clicks are ignored, and most key presses are ignored too.

  Workaround is to press super to enter shell overview, then super again
  to close, and mouse clicks will begin working again.

  gnome-shell 42~beta-1ubuntu2 from -proposed.

  [Testcase]

  1) Leave your system idle, until the screen starts fading to black
  2) As the screen is fading to black, move the mouse to prevent screensaver.
  3) Attempt to click any window or type something

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964545/+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 1965639] Re: purple screen after login using fingerprint

[Daniel van Vugt]

Thanks for the bug report.

Next time the screen stays purple, please:

1. Wait 10 seconds.

2. Reboot and login with password.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. Look in /var/crash for crash files and if found run:

   ubuntu-bug YOURFILE.crash

   Then tell us the ID of the newly-created bug.

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


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

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

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

Title:
  purple screen after login using fingerprint

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I updated the machine yesterday, and additionally added the
  fingerprint to pam using pam-auth-update. The screen now stays purple
  after logging in using the finger, but works fine after logging in
  using the password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 19 21:37:43 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.103.01, 5.13.0-28-generic, x86_64: installed
   nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2294]
  InstallationDate: Installed on 2020-12-10 (464 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20NN002NGE
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=2bcb2bd8-2364-4f28-9085-f6c366d45c6d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2021
  dmi.bios.release: 1.89
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2LET89W (1.89 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NN002NGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2LET89W(1.89):bd11/24/2021:br1.89:efr1.20:svnLENOVO:pn20NN002NGE:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20NN_BU_Think_FM_ThinkPadX390Yoga:
  dmi.product.family: ThinkPad X390 Yoga
  dmi.product.name: 20NN002NGE
  dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga
  dmi.product.version: ThinkPad X390 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965639/+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 1965627] Re: Unlock screen password is barely visible/contrasting

[Launchpad Bug Tracker]

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

** Changed in: yaru-theme (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/1965627

Title:
  Unlock screen password is barely visible/contrasting

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  Returning from suspend login screen password field  barely visible.
  see attachment.
  corrado@corrado-p5-jj-0203:~$ inxi -Fx
  System:
Host: corrado-p5-jj-0203 Kernel: 5.15.0-23-generic x86_64 bits: 64
  compiler: gcc v: 11.2.0 Desktop: GNOME 42.beta
  Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:
Type: Desktop Mobo: Gigabyte model: H87M-D3H v: x.x
  serial:  UEFI: American Megatrends v: F3
  date: 04/24/2013
  CPU:
Info: dual core model: Intel Core i3-4130 bits: 64 type: MT MCP
  arch: Haswell rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2195 high: 2196 min/max: 800/3400 cores: 1: 2195
  2: 2195 3: 2195 4: 2196 bogomips: 27136
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
  vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0
Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  gpu: i915 resolution: 1680x1050~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2)
  v: 4.5 Mesa 21.3.5 direct render: Yes
  Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel v: kernel bus-ID: 00:03.0
Device-2: Intel 8 Series/C220 Series High Definition Audio
  vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
Sound Server-1: ALSA v: k5.15.0-23-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Gigabyte driver: r8169 v: kernel port: e000 bus-ID: 02:00.0
IF: enp2s0 state: down mac: 94:de:80:7e:90:a7
Device-2: D-Link DWA-121 802.11n Wireless N 150 Pico Adapter [Realtek
RTL8188CUS]
  type: USB driver: rtl8192cu bus-ID: 3-14:5
IF: wlx48ee0c2322b8 state: up mac: 48:ee:0c:23:22:b8
  Drives:
Local Storage: total: 1.14 TiB used: 11.51 GiB (1.0%)
ID-1: /dev/sda vendor: Crucial model: CT250MX500SSD1 size: 232.89 GiB
ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB
  Partition:
ID-1: / size: 16.21 GiB used: 11.5 GiB (71.0%) fs: ext4 dev: /dev/sda5
ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat
  dev: /dev/sda1
  Swap:
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) dev: /dev/sdb2
  Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
  Info:
Processes: 246 Uptime: 5h 28m Memory: 7.65 GiB used: 2.08 GiB (27.2%)
Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1869 Shell: Bash
v: 5.1.16 inxi: 3.3.13
  corrado@corrado-p5-jj-0203:~$ 

  Note: I'm unsure package is gdm3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 41.3-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 19 17:18:46 2022
  InstallationDate: Installed on 2022-02-08 (39 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  SourcePackage: gdm3
  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/1965627/+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 1965627] Re: Unlock screen password is barely visible/contrasting

[Daniel van Vugt]

** Summary changed:

- Returning from suspend login screen password  barely visible
+ Unlock screen password is barely visible/contrasting

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

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unlock screen password is barely visible/contrasting

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  Returning from suspend login screen password field  barely visible.
  see attachment.
  corrado@corrado-p5-jj-0203:~$ inxi -Fx
  System:
Host: corrado-p5-jj-0203 Kernel: 5.15.0-23-generic x86_64 bits: 64
  compiler: gcc v: 11.2.0 Desktop: GNOME 42.beta
  Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:
Type: Desktop Mobo: Gigabyte model: H87M-D3H v: x.x
  serial:  UEFI: American Megatrends v: F3
  date: 04/24/2013
  CPU:
Info: dual core model: Intel Core i3-4130 bits: 64 type: MT MCP
  arch: Haswell rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2195 high: 2196 min/max: 800/3400 cores: 1: 2195
  2: 2195 3: 2195 4: 2196 bogomips: 27136
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
  vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0
Display: wayland server: X.Org v: 1.22.1 with: Xwayland v: 22.1.0
  compositor: gnome-shell driver: X: loaded: modesetting unloaded: 
fbdev,vesa
  gpu: i915 resolution: 1680x1050~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2)
  v: 4.5 Mesa 21.3.5 direct render: Yes
  Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel v: kernel bus-ID: 00:03.0
Device-2: Intel 8 Series/C220 Series High Definition Audio
  vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
Sound Server-1: ALSA v: k5.15.0-23-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Gigabyte driver: r8169 v: kernel port: e000 bus-ID: 02:00.0
IF: enp2s0 state: down mac: 94:de:80:7e:90:a7
Device-2: D-Link DWA-121 802.11n Wireless N 150 Pico Adapter [Realtek
RTL8188CUS]
  type: USB driver: rtl8192cu bus-ID: 3-14:5
IF: wlx48ee0c2322b8 state: up mac: 48:ee:0c:23:22:b8
  Drives:
Local Storage: total: 1.14 TiB used: 11.51 GiB (1.0%)
ID-1: /dev/sda vendor: Crucial model: CT250MX500SSD1 size: 232.89 GiB
ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB
  Partition:
ID-1: / size: 16.21 GiB used: 11.5 GiB (71.0%) fs: ext4 dev: /dev/sda5
ID-2: /boot/efi size: 252 MiB used: 5.2 MiB (2.1%) fs: vfat
  dev: /dev/sda1
  Swap:
ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) dev: /dev/sdb2
  Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
  Info:
Processes: 246 Uptime: 5h 28m Memory: 7.65 GiB used: 2.08 GiB (27.2%)
Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1869 Shell: Bash
v: 5.1.16 inxi: 3.3.13
  corrado@corrado-p5-jj-0203:~$ 

  Note: I'm unsure package is gdm3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 41.3-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 19 17:18:46 2022
  InstallationDate: Installed on 2022-02-08 (39 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  SourcePackage: gdm3
  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/1965627/+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 1965563] Re: Can't open extensions app

[Daniel van Vugt]

Seems to be working in both Wayland and Xorg sessions here.

Although I must say it wasn't working for me for a couple of days last
week, around the time this bug was created.


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

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

Title:
  Can't open extensions app

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1964493] Re: gdm has a dark grey (gray) background now

[Daniel van Vugt]

Won't fix per the upstream bug
https://github.com/ubuntu/yaru/issues/3473

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  gdm has a dark grey (gray) background now

Status in Yaru Theme:
  New
Status in yaru-theme package in Ubuntu:
  Won't Fix

Bug description:
  Using the GNOME 42 updates in proposed the login screen background is
  black, that feels buggy, we should revert to the old style

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1964493/+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 1965727] [NEW] [jammy] Purple background is visible briefly during the login animation

[Daniel van Vugt]

Public bug reported:

Purple background is visible briefly during the login animation.

The hard-coded system background colour needs to be updated to match the
new grey login screen in jammy.

** Affects: gnome-shell (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: jammy visual-quality

** Description changed:

  Purple background is visible briefly during the login animation.
  
- It needs to be updated to match the new grey login screen in jammy.
+ The hard-coded system background colour needs to be updated to match the
+ new grey login screen in jammy.

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

Title:
  [jammy] Purple background is visible briefly during the login
  animation

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Purple background is visible briefly during the login animation.

  The hard-coded system background colour needs to be updated to match
  the new grey login screen in jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965727/+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 1965219] Re: gnome lock screen does not permit reentering password

[Daniel van Vugt]

In that case, next time the problem happens please reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


-- 
Mailing list: 

[Desktop-packages] [Bug 1965662] Re: gnome-shell: Unhandled promise rejection in checkInvocation@resource:///org/gnome/shell/misc/util.js:544:26

[Daniel van Vugt]

** Summary changed:

- gnome-shell[3452]: Unhandled promise rejection
+ gnome-shell: Unhandled promise rejection in 
checkInvocation@resource:///org/gnome/shell/misc/util.js:544:26

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

Title:
  gnome-shell: Unhandled promise rejection in
  checkInvocation@resource:///org/gnome/shell/misc/util.js:544:26

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 development branch @ 20/03/2022

  opening gnome settings tab Appearance

  picking other yaru theme colors invoke errors:

  mrt 20 09:07:08 R00TB00K gnome-shell[3452]: Unhandled promise rejection. 
To suppress this warning, add an error handler to your promise chain with 
.catch() or a try-catch block around your await expression. Stack trace of the 
failed promise:

checkInvocation@resource:///org/gnome/shell/misc/util.js:544:26

ScreenTransitionAsync@resource:///org/gnome/shell/ui/shellDBus.js:256:33

_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35

_wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 09:33:09 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
[modified]
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965662/+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 1965696] Re: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions

[Daniel van Vugt]

** Summary changed:

- Keyboard navigation after pressing Ctrl+Alt+Tab doesn't work in Xorg sessions
+ Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg 
sessions

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

Title:
  Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work
  in Xorg sessions

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  As of 2 days ago, I can no longer quickly get to system controls such
  as the Top Bar using the keyboard.  According to the keyboard
  shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to
  access these controls.  When I press this key combination, I'm told by
  the Orca screen reader that I'm on the Top Bar. When I release the
  keys, focus jumps back to the window I was in before. I do not know if
  this is the case without Orca running. I'm unable to test without Orca
  running. I've reset Gnome settings, with no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  Uname: Linux 5.16.11-76051611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 13:01:07 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (1420 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1965696/+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 1926256] Re: Pasted text in the terminal is always highlighted and selected

[Martin Wimpress ]

** Changed in: mate-terminal (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Pasted text in the terminal is always highlighted and selected

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in mate-terminal package in Ubuntu:
  Invalid
Status in readline package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 21.04 installed
  2. Launch terminal
  3a. Execute some command, select this command to copy it, then paste command
  3b. Paste some command from clipboard to terminal

  Expected result:
  * pasted command is not highlighted and is not selected

  Actual result:
  * pasted command is selected and highlighted

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  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
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Apr 27 09:43:56 2021
  InstallationDate: Installed on 2021-04-23 (3 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+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 1965696] Re: Keyboard navigation after pressing Ctrl+Alt+Tab doesn't work in Xorg sessions

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

Title:
  Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work
  in Xorg sessions

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  As of 2 days ago, I can no longer quickly get to system controls such
  as the Top Bar using the keyboard.  According to the keyboard
  shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to
  access these controls.  When I press this key combination, I'm told by
  the Orca screen reader that I'm on the Top Bar. When I release the
  keys, focus jumps back to the window I was in before. I do not know if
  this is the case without Orca running. I'm unable to test without Orca
  running. I've reset Gnome settings, with no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  Uname: Linux 5.16.11-76051611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 13:01:07 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (1420 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1965696/+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 1965696] Re: Keyboard navigation after pressing Ctrl+Alt+Tab doesn't work in Xorg sessions

[Daniel van Vugt]

Logging info a Wayland session appears to avoid the bug.

** Summary changed:

- Unable to quickly access system controls such as Top Bar using keyboard
+ Keyboard navigation after pressing Ctrl+Alt+Tab doesn't work in Xorg sessions

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

Title:
  Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work
  in Xorg sessions

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  As of 2 days ago, I can no longer quickly get to system controls such
  as the Top Bar using the keyboard.  According to the keyboard
  shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to
  access these controls.  When I press this key combination, I'm told by
  the Orca screen reader that I'm on the Top Bar. When I release the
  keys, focus jumps back to the window I was in before. I do not know if
  this is the case without Orca running. I'm unable to test without Orca
  running. I've reset Gnome settings, with no change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  Uname: Linux 5.16.11-76051611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 13:01:07 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (1420 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  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/1965696/+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 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal

[Daniel van Vugt]

The log message in comment #2 is bug 1965673. I'm seeing it in
everyone's logs today, including my own. And without using password
dialogs. So unassigning ibus here. Use bug 1965673 for that.

** No longer affects: ibus (Ubuntu)

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

Title:
  [jammy][regression] gnome-shell PolicyKit password prompt sends
   keys to the terminal

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This is a regression not seen until this week (not seen until March 4
  at least).  Calling debsign from a terminal pops up the window to
  enter the key, but the terminal is sent continuous  keys and
  the terminal scrolls down with empty input lines. You can still sign
  the file, however you end up with an empty scroll buffer if the
  signing takes too long time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+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 1965673] Re: Object 0x557aa9440850 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management

[Daniel van Vugt]

** Bug watch added: github.com/ibus/ibus/issues #2387
   https://github.com/ibus/ibus/issues/2387

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2387
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Object 0x557aa9440850 of type IBusText has been finalized while it was still 
owned by gjs, this is due to invalid memory management
+ Object 0x... of type IBusText has been finalized while it was still owned by 
gjs, this is due to invalid memory management

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

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

Title:
  Object 0x... of type IBusText has been finalized while it was still
  owned by gjs, this is due to invalid memory management

Status in ibus:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 development branch @ 20/03/2022

  Journal logs spam a lot of lines like these:

  mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x7f896cf7cad0 of type 
IBusText has been finalized while it was still owned by gjs, this is due to 
invalid memory management. 
  mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x557a992efd20 of type 
IBusText has been finalized while it was still owned by gjs, this is due to 
invalid memory management

  
  Probably regression bug upstream: 

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

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 20 13:34:37 2022
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1965673/+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 1965699] Re: Whole desktop crashes after closing laptop lid about every 2 times. Gives error "failed to enable link training"

[Daniel van Vugt]

Thanks for the bug report.

"failed to enable link training" would probably be a kernel error logged
by the graphics driver. So that may be a kernel/driver bug, or if you
use an external monitor then maybe a cable problem.

Next time the problem happens please reboot as usual and then:

1. Run:

   journalctl -b-1 > prevboot.txt

2. Attach the resulting text file here.

3. Run:

   apport-collect 1965699

4. Look in /var/crash for crash files and if found run:

   ubuntu-bug YOURFILE.crash

   Then tell us the ID of the newly-created bug.

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

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

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

Title:
  Whole desktop crashes after closing laptop lid about every 2 times.
  Gives error "failed to enable link training"

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have an Asus Zenbook Duo, with an Intel Core i5-10210U with a mix of both 
integrated and dedicated graphics.
  My dedicated graphics is an Nvidia Geforce MX250.

  About every two times I shut the lid of my laptop, I get no desktop
  with the error on the screen and no ability to do anything. I am
  forced to reboot.

  Please help!
  Worth mentioning that I am new to linux :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965699/+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 1965699] Re: Whole desktop crashes after closing laptop lid about every 2 times. Gives error "failed to enable link training"

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1965699

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

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

Title:
  Whole desktop crashes after closing laptop lid about every 2 times.
  Gives error "failed to enable link training"

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have an Asus Zenbook Duo, with an Intel Core i5-10210U with a mix of both 
integrated and dedicated graphics.
  My dedicated graphics is an Nvidia Geforce MX250.

  About every two times I shut the lid of my laptop, I get no desktop
  with the error on the screen and no ability to do anything. I am
  forced to reboot.

  Please help!
  Worth mentioning that I am new to linux :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965699/+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 1965219] Re: gnome lock screen does not permit reentering password

[Jeff Burdges]

oops alright.  I've no gnome-shell reports in /var/crash only another
systemd-timesyncd report.

I don't think gnome-ghell is crashing, but sometimes just stuck when
emerging from suspend.

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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: