[Desktop-packages] [Bug 1995173] Re: Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue

[Yosua Liu]

** Description changed:

  The device is Lenovo Legion 7. This laptop has a mux switch to switch
  between dynamic/hybrid or discrete graphics mode. This laptop has a high
  resolution with high pixel density than the other displays out there,
  but I don't know the exact number. Additionally, this laptop can adjust
  the display refresh rate between 60 and 165 Hz.
  
  ---
  
  There were 1 problem I encountered in dynamic/hybrid graphics mode:
  
  - The widgets shown were too small.
  
  Details:
  
  The resolution was correct, at 2560x1600, but all widgets shown were too
  small. I suspected this was due to the laptop screen high pixel density
  and the widget size calculation didn't make use of physical dimension,
  but in terms of pixel.
  
  I thought installing NVIDIA driver would fix this, but no; this worked
  in OpenSUSE Leap with KDE Plasma and I think it was because of the
  inclusion of NVIDIA OpenGL driver.
  
  The current workaround was to scale by 200% in "Display Settings",
  although the login screen isn't affected by the scaling at all.
  
  ---
  
  There were 3 problems I encountered in discrete graphics mode:
  
  - The widgets were are too small, like the hybrid graphics mode issue.
  - The DE seemed to use wrong screen refresh rate.
  
  The refresh rate was fixed at 93 Hz in the "Display Settings".
  
  Changing the refresh rate between 60 Hz and 165 Hz by Fn keys didn't
  update the 93 Hz in the "Display Settings".
  
  This didn't happen in the hybrid graphics mode.
  
  OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I
  think it may be either GNOME DE or xorg misconfigurations.
- 
- Details:
- 
- The above 2 problems were the same issue as encountered in the hybrid
- graphics mode.
  
  - Screen brightness was fixed at 100%.
  
  Details:
  
  Screen brightness could be adjusted by the keyboard Fn keys, but the
  brightness was fixed at 100%.
  
  This didn't happen in the hybrid graphics mode.
  
  This is the most annoying problem and have forced me to use the hybrid
  graphics mode which I don't like.
  
  My first thought was either a specific NVIDIA issue or xorg
  misconfigurations.
  
  So I tried adding "acpi_backlight=vendor" and
  "nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but
  didn't work at all.
  
  ---
  
  In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed
  below:
  
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, 
During name lookup/catalog (20210730/psobject-220)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading 
X.509 certificate -65
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  
  In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above
  except that there was no:
  
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  520.56.06  Release 
Build  (dvs-builder@U16-T12-10-2)  Thu Oct  6 21:33:54 UTC 2022
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 29 18:50:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/520.56.06, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev 
a1) (prog-if 00 [VGA controller])

[Desktop-packages] [Bug 1995173] Re: Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue

[Yosua Liu]

** Description changed:

  The device is Lenovo Legion 7. This laptop has a mux switch to switch
  between dynamic/hybrid or discrete graphics mode. This laptop has a high
  resolution with high pixel density than the other displays out there,
  but I don't know the exact number. Additionally, this laptop can adjust
  the display refresh rate between 60 and 165 Hz.
  
  ---
  
- There were 2 problems I encountered in dynamic/hybrid graphics mode:
+ There were 1 problem I encountered in dynamic/hybrid graphics mode:
  
  - The widgets shown were too small.
  
  Details:
  
  The resolution was correct, at 2560x1600, but all widgets shown were too
  small. I suspected this was due to the laptop screen high pixel density
  and the widget size calculation didn't make use of physical dimension,
  but in terms of pixel.
  
  I thought installing NVIDIA driver would fix this, but no; this worked
  in OpenSUSE Leap with KDE Plasma and I think it was because of the
  inclusion of NVIDIA OpenGL driver.
  
  The current workaround was to scale by 200% in "Display Settings",
- although this make some widgets pixelated or blurred and the login
- screen isn't affected by the scaling at all.
- 
- - The DE seemed to use wrong screen refresh rate.
- 
- The refresh rate I usually used is 165 Hz, but the "Display Settings"
- showed 93 Hz.
- 
- Changing the refresh rate between 60 Hz and 165 Hz didn't update the 93
- Hz in the "Display Settings".
- 
- OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I
- think it may be either GNOME DE or xorg misconfigurations.
+ although the login screen isn't affected by the scaling at all.
  
  ---
  
  There were 3 problems I encountered in discrete graphics mode:
  
- - The widgets were are too small.
+ - The widgets were are too small, like the hybrid graphics mode issue.
  - The DE seemed to use wrong screen refresh rate.
+ 
+ The refresh rate was fixed at 93 Hz in the "Display Settings".
+ 
+ Changing the refresh rate between 60 Hz and 165 Hz by Fn keys didn't
+ update the 93 Hz in the "Display Settings".
+ 
+ This didn't happen in the hybrid graphics mode.
+ 
+ OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I
+ think it may be either GNOME DE or xorg misconfigurations.
  
  Details:
  
  The above 2 problems were the same issue as encountered in the hybrid
  graphics mode.
  
  - Screen brightness was fixed at 100%.
  
  Details:
  
- Screen brightness could be adjusted by the keyboard fn keys, but the
+ Screen brightness could be adjusted by the keyboard Fn keys, but the
  brightness was fixed at 100%.
+ 
+ This didn't happen in the hybrid graphics mode.
  
  This is the most annoying problem and have forced me to use the hybrid
  graphics mode which I don't like.
  
- My first thought was a specific NVIDIA issue.
+ My first thought was either a specific NVIDIA issue or xorg
+ misconfigurations.
  
  So I tried adding "acpi_backlight=vendor" and
  "nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but
  didn't work at all.
  
  ---
  
  In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed
  below:
  
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, 
During name lookup/catalog (20210730/psobject-220)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading 
X.509 certificate -65
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  
  In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above
  except that there was no:
  
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  520.56.06  

[Desktop-packages] [Bug 1987976]

[Alan Jenkins]

(In reply to Robert Mader [:rmader] from comment #42)
> Hm, this pretty much sounds like Gnome-Shell bug around Xwayland-on-demand to 
> me - so maybe a better place for that would be 
> https://gitlab.gnome.org/GNOME/mutter/-/issues (or a Ubuntu bug, in case they 
> ship some custom patches).

...

> Thanks @sourcejedi! I've so far been unable to reproduce this on four
different systems with Fedora 36 or Manjaro,

Hi Robert. I got a new reproducer for Firefox, which doesn't use
Xwayland.  I ran this on my Fedora 36 system, the system that required a
quick hand to reproduce with my .desktop file method.

WARNING for people with photosensitive epilepsy. This will cause full-
screen flickering.

1. Make sure user X is logged out, or at least not running Firefox.
2. Switch to a text console (ctrl + alt + f6) and log in.
3. `startx /usr/bin/fvwm`
4. Left click on the desktop to open the app menu. Open an xterm.
5. Open a second xterm.
6. In xterm 1, run `while true; do picom; sleep 0.1; killall picom; done`. The 
screen will now start flickering.
7. In xterm 2, run `firefox`

Result: Firefox doesn't draw anything inside its window, or is
completely black.

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

Title:
  firefox black window

Status in Mozilla Firefox:
  New
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987981] Re: nautilus crashed with SIGSEGV in g_str_hash()

[Launchpad Bug Tracker]

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

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

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

Title:
  nautilus crashed with SIGSEGV in g_str_hash()

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  nothing

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43~beta.1-2ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 16:25:29 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-08-28 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220828)
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=de_CH:de
   LANG=de_CH.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9f0cc15434 : movsbl (%rdi),%edx
   PC (0x7f9f0cc15434) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_str_hash () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_contains () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgtk-4.so.1
   () at /lib/x86_64-linux-gnu/libgtk-4.so.1
   () at /lib/x86_64-linux-gnu/libgtk-4.so.1
  Title: nautilus crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:
   
  usr_lib_nautilus:
   file-roller   43~alpha-1
   nautilus-extension-gnome-terminal 3.45.90-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987981/+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 1921920] Re: Xubuntu 20.04.2.1 cannot log out, shut down or restart from a temporary guest session.

[Sean Davis]

** Package changed: xubuntu-meta (Ubuntu) => xfce4-session (Ubuntu)

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

Title:
  Xubuntu 20.04.2.1 cannot log out, shut down or restart from a
  temporary guest session.

Status in lightdm package in Ubuntu:
  New
Status in xfce4-session package in Ubuntu:
  New

Bug description:
  I cannot log out, shut down or restart from an activated temporary guest 
session. Only via tty or REISUB. Clicking anything in the 
logout/restart/shutdown GUI dialog window will only result in the message "An 
error occurred while logging out"
  GDBus.Error:org.freedesktop.Dbus.Error.InvalidArgs: Type ofmessage, "(yb)", 
does not match expected type "(b)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1921920/+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 1985869] Re: Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found]

[Cyrus Lien]

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

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

Title:
  Screen does not update [Failed to post KMS update: CRTC property
  (GAMMA_LUT) not found and  Page flip discarded: CRTC property
  (GAMMA_LUT) not found]

Status in Mutter:
  New
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  == ApportVersion =
  2.20.11-0ubuntu82.1

  == Architecture =
  amd64

  == CasperMD5CheckResult =
  pass

  == Date =
  Fri Aug 12 16:01:31 2022

  == Dependencies =
  accountsservice 22.07.5-2ubuntu1.3
  acl 2.3.1-1
  adduser 3.118ubuntu5
  adwaita-icon-theme 41.0-1ubuntu1
  alsa-topology-conf 1.2.5.1-2
  alsa-ucm-conf 1.2.6.3-1ubuntu1
  apg 2.2.3.dfsg.1-5build2
  apport 2.20.11-0ubuntu82.1
  apport-symptoms 0.24
  apt 2.4.6
  apt-utils 2.4.6
  aptdaemon 1.1.1+bzr982-0ubuntu39
  aptdaemon-data 1.1.1+bzr982-0ubuntu39
  aspell 0.60.8-4build1
  aspell-en 2018.04.16-0-1
  at-spi2-core 2.44.0-3
  avahi-daemon 0.8-5ubuntu5
  avahi-utils 0.8-5ubuntu5
  base-files 12ubuntu4.2
  bash 5.1-6ubuntu1
  bash-completion 1:2.11-5ubuntu1
  bind9-host 1:9.18.1-1ubuntu1.1
  bind9-libs 1:9.18.1-1ubuntu1.1
  bluez 5.64-0ubuntu1
  bolt 0.9.2-1
  bsdextrautils 2.37.2-4ubuntu3
  bubblewrap 0.6.1-1
  ca-certificates 20211016
  cheese-common 41.1-1build1
  colord 1.4.6-1
  colord-data 1.4.6-1
  coreutils 8.32-4.1ubuntu1
  cpp 4:11.2.0-1ubuntu1
  cpp-11 11.2.0-19ubuntu1
  cracklib-runtime 2.9.6-3.4build4
  cups-pk-helper 0.2.6-1ubuntu5

  [ 6902.723370] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7123.822417] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7123.823384] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7124.335913] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize 
fprintd service: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
net.reactivated.Fprint was not provided by any .service files

asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  [ 7180.309459] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7180.311605] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7218.558479] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7218.559502] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7244.319195] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7244.320182] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7295.446436] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7295.447812] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7573.588299] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7573.590411] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7574.868039] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize 
fprintd service: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
net.reactivated.Fprint was not provided by any .service files

asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  [ 7654.509594] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7654.510955] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7751.955703] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7751.957582] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7965.552231] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7965.553842] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 8073.130242] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 8073.131334] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 8816.510259] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 8816.511259] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 8818.963154] ubuntu1 gnome-shell[2773]: JS 

[Desktop-packages] [Bug 1985869] Re: Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found]

[Yuan-Chen Cheng]

** Tags added: oem-priority

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

Title:
  Screen does not update [Failed to post KMS update: CRTC property
  (GAMMA_LUT) not found and  Page flip discarded: CRTC property
  (GAMMA_LUT) not found]

Status in Mutter:
  New
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  == ApportVersion =
  2.20.11-0ubuntu82.1

  == Architecture =
  amd64

  == CasperMD5CheckResult =
  pass

  == Date =
  Fri Aug 12 16:01:31 2022

  == Dependencies =
  accountsservice 22.07.5-2ubuntu1.3
  acl 2.3.1-1
  adduser 3.118ubuntu5
  adwaita-icon-theme 41.0-1ubuntu1
  alsa-topology-conf 1.2.5.1-2
  alsa-ucm-conf 1.2.6.3-1ubuntu1
  apg 2.2.3.dfsg.1-5build2
  apport 2.20.11-0ubuntu82.1
  apport-symptoms 0.24
  apt 2.4.6
  apt-utils 2.4.6
  aptdaemon 1.1.1+bzr982-0ubuntu39
  aptdaemon-data 1.1.1+bzr982-0ubuntu39
  aspell 0.60.8-4build1
  aspell-en 2018.04.16-0-1
  at-spi2-core 2.44.0-3
  avahi-daemon 0.8-5ubuntu5
  avahi-utils 0.8-5ubuntu5
  base-files 12ubuntu4.2
  bash 5.1-6ubuntu1
  bash-completion 1:2.11-5ubuntu1
  bind9-host 1:9.18.1-1ubuntu1.1
  bind9-libs 1:9.18.1-1ubuntu1.1
  bluez 5.64-0ubuntu1
  bolt 0.9.2-1
  bsdextrautils 2.37.2-4ubuntu3
  bubblewrap 0.6.1-1
  ca-certificates 20211016
  cheese-common 41.1-1build1
  colord 1.4.6-1
  colord-data 1.4.6-1
  coreutils 8.32-4.1ubuntu1
  cpp 4:11.2.0-1ubuntu1
  cpp-11 11.2.0-19ubuntu1
  cracklib-runtime 2.9.6-3.4build4
  cups-pk-helper 0.2.6-1ubuntu5

  [ 6902.723370] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7123.822417] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7123.823384] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7124.335913] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize 
fprintd service: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
net.reactivated.Fprint was not provided by any .service files

asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  [ 7180.309459] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7180.311605] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7218.558479] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7218.559502] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7244.319195] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7244.320182] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7295.446436] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7295.447812] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7573.588299] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7573.590411] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7574.868039] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize 
fprintd service: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
net.reactivated.Fprint was not provided by any .service files

asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  [ 7654.509594] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7654.510955] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7751.955703] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7751.957582] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7965.552231] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7965.553842] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 8073.130242] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 8073.131334] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 8816.510259] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 8816.511259] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 8818.963154] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize 
fprintd 

[Desktop-packages] [Bug 1985869] Re: Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found]

[Cyrus Lien]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   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/1985869

Title:
  Screen does not update [Failed to post KMS update: CRTC property
  (GAMMA_LUT) not found and  Page flip discarded: CRTC property
  (GAMMA_LUT) not found]

Status in Mutter:
  New
Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  == ApportVersion =
  2.20.11-0ubuntu82.1

  == Architecture =
  amd64

  == CasperMD5CheckResult =
  pass

  == Date =
  Fri Aug 12 16:01:31 2022

  == Dependencies =
  accountsservice 22.07.5-2ubuntu1.3
  acl 2.3.1-1
  adduser 3.118ubuntu5
  adwaita-icon-theme 41.0-1ubuntu1
  alsa-topology-conf 1.2.5.1-2
  alsa-ucm-conf 1.2.6.3-1ubuntu1
  apg 2.2.3.dfsg.1-5build2
  apport 2.20.11-0ubuntu82.1
  apport-symptoms 0.24
  apt 2.4.6
  apt-utils 2.4.6
  aptdaemon 1.1.1+bzr982-0ubuntu39
  aptdaemon-data 1.1.1+bzr982-0ubuntu39
  aspell 0.60.8-4build1
  aspell-en 2018.04.16-0-1
  at-spi2-core 2.44.0-3
  avahi-daemon 0.8-5ubuntu5
  avahi-utils 0.8-5ubuntu5
  base-files 12ubuntu4.2
  bash 5.1-6ubuntu1
  bash-completion 1:2.11-5ubuntu1
  bind9-host 1:9.18.1-1ubuntu1.1
  bind9-libs 1:9.18.1-1ubuntu1.1
  bluez 5.64-0ubuntu1
  bolt 0.9.2-1
  bsdextrautils 2.37.2-4ubuntu3
  bubblewrap 0.6.1-1
  ca-certificates 20211016
  cheese-common 41.1-1build1
  colord 1.4.6-1
  colord-data 1.4.6-1
  coreutils 8.32-4.1ubuntu1
  cpp 4:11.2.0-1ubuntu1
  cpp-11 11.2.0-19ubuntu1
  cracklib-runtime 2.9.6-3.4build4
  cups-pk-helper 0.2.6-1ubuntu5

  [ 6902.723370] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7123.822417] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7123.823384] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7124.335913] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize 
fprintd service: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
net.reactivated.Fprint was not provided by any .service files

asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  [ 7180.309459] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7180.311605] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7218.558479] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7218.559502] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7244.319195] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7244.320182] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7295.446436] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7295.447812] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7573.588299] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7573.590411] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7574.868039] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize 
fprintd service: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
net.reactivated.Fprint was not provided by any .service files

asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  [ 7654.509594] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7654.510955] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7751.955703] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7751.957582] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 7965.552231] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 7965.553842] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 8073.130242] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 8073.131334] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 
(GAMMA_LUT) not found
  [ 8816.510259] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC 
property (GAMMA_LUT) not found
  [ 8816.511259] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property 

[Desktop-packages] [Bug 1789114] Re: [i965] [SNB] Screen flickering continuous horizontal bars repainting

[Launchpad Bug Tracker]

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

** Changed in: mutter (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/1789114

Title:
  [i965] [SNB] Screen flickering continuous horizontal bars repainting

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

Bug description:
  https://bugs.launchpad.net/ubuntu/+bug/1786502
  This is inreference to the above bug

  Performed https://bugs.launchpad.net/ubuntu/+bug/1786502

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 26 10:07:02 2018
  DisplayManager: gdm3
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-28 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789114/+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 1789114] Re: [i965] [SNB] Screen flickering continuous horizontal bars repainting

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

Title:
  [i965] [SNB] Screen flickering continuous horizontal bars repainting

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

Bug description:
  https://bugs.launchpad.net/ubuntu/+bug/1786502
  This is inreference to the above bug

  Performed https://bugs.launchpad.net/ubuntu/+bug/1786502

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 26 10:07:02 2018
  DisplayManager: gdm3
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-28 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789114/+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 1977782] Re: Unable to open any file:/// URL

[Daniel Hatton]

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

To answer @me-again's question: if one uses the File menu->Open file
facility in an attempt to open a file in /tmp, then Firefox copies the
file to a newly-created directory in the /run/user hierarchy, and opens
that new copy of the file with a file:// URI.

This problem appears to be a side-effect of some sort of attempt by the
Firefox developers to mitigate the security vulnerability described at
.

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

Title:
  Unable to open any file:/// URL

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The way this configures/installs the snap makes it impossible to open
  any file either from the command-line or by specifying a link of the
  file:/// kind.  That makes firefox unusable for browsing local HTML
  documentation.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-35.36-lowlatency 5.15.35
  Uname: Linux 5.15.0-35-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Jun  7 02:27:27 2022
  InstallationDate: Installed on 2011-10-14 (3888 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-01-28 (130 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1977782/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Didier L]

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

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
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:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Launchpad Bug Tracker]

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

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

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
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:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1977782] Re: Unable to open any file:/// URL

[Daniel Hatton]

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

I don't think this is a duplicate of #1790608.  #1790608 concerns
launching an external file handler from Firefox, whereas this bug
concerns launching Firefox from an external workflow, to handle a
locally-stored HTML file.

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

Title:
  Unable to open any file:/// URL

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The way this configures/installs the snap makes it impossible to open
  any file either from the command-line or by specifying a link of the
  file:/// kind.  That makes firefox unusable for browsing local HTML
  documentation.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-35.36-lowlatency 5.15.35
  Uname: Linux 5.15.0-35-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Jun  7 02:27:27 2022
  InstallationDate: Installed on 2011-10-14 (3888 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-01-28 (130 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1977782/+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 1961508] Re: Dock displaying over window after resuming from blank screen

[Ars Ivci]

This bug affects 22.10 as well. In addition to restoring and re-
maximizing the windows, one can also hide and re-unhide the dock and/or
switching the panel mode off and back to on.

On 22.04 and 22.10, switching to xorg, corrects the problem in my case.
However, on 22.04 only, this messes with the color profile, resulting in
phosphorous colors. Removing the profile and using the system without
one (not calibrated) remedies the situation (probably requires a log
out/in or reboot).

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 1995073] Re: Ubuntu 22.10 deja-dup throws exception when login

[Michael Terry]

If you install python3-pydrive does that error go away?

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

Title:
  Ubuntu 22.10 deja-dup throws exception when login

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Can't login and restore from GDrive. See attached picture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1995073/+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 1995181] [NEW] Desktop suddenly completely unresponsive.

[Alexander Dejaco]

Public bug reported:

Desktop suddenly becomes completely unresponsive.
Only ssh is possible. Hard Reset is necessary, loss of all data which cannot be 
saved via cli.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xserver-xorg-video-nouveau 1:1.0.17-2build1
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sat Oct 29 17:34:02 2022
DistUpgraded: 2022-08-14 17:52:12,654 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 sysdig/0.27.1, 5.15.0-48-generic, x86_64: installed
 sysdig/0.27.1, 5.15.0-52-generic, x86_64: installed
 virtualbox/6.1.38, 5.15.0-48-generic, x86_64: installed
 virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: Dell HD Graphics 530 [1028:06e3]
 NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1138]
InstallationDate: Installed on 2017-12-09 (1784 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Alienware Alienware X51 R3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=884d86c6-de1e-4066-b108-9caf3003bbe5 ro quiet splash 
resume=UUID=a28b5191-1b6c-44ec-b492-73fbd2b68842 vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: Upgraded to jammy on 2022-08-14 (75 days ago)
dmi.bios.date: 05/25/2017
dmi.bios.release: 5.11
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.10
dmi.board.name: 026CD3
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Alienware
dmi.ec.firmware.release: 15.7
dmi.modalias: 
dmi:bvnAlienware:bvr1.2.10:bd05/25/2017:br5.11:efr15.7:svnAlienware:pnAlienwareX51R3:pvr:rvnAlienware:rn026CD3:rvrA00:cvnAlienware:ct3:cvr:sku6e3:
dmi.product.name: Alienware X51 R3
dmi.product.sku: 6e3
dmi.sys.vendor: Alienware
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy possible-manual-nvidia-install ubuntu

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

Title:
  Desktop suddenly completely unresponsive.

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Desktop suddenly becomes completely unresponsive.
  Only ssh is possible. Hard Reset is necessary, loss of all data which cannot 
be saved via cli.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xserver-xorg-video-nouveau 1:1.0.17-2build1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Oct 29 17:34:02 2022
  DistUpgraded: 2022-08-14 17:52:12,654 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   sysdig/0.27.1, 5.15.0-48-generic, x86_64: installed
   sysdig/0.27.1, 5.15.0-52-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-48-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Dell HD Graphics 530 [1028:06e3]
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1138]
  InstallationDate: Installed on 2017-12-09 (1784 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Alienware Alienware X51 R3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=884d86c6-de1e-4066-b108-9caf3003bbe5 ro quiet splash 
resume=UUID=a28b5191-1b6c-44ec-b492-73fbd2b68842 vt.handoff=7
  RebootRequiredPkgs: Error: path 

[Desktop-packages] [Bug 1724037] Re: Allow GNOME fractional scaling below 100%

[Dark Dragon]

@james-fsck you need to adapt the position values (x,y) as well to the
scale as I outlined in the linked upstream issue:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1465#note_1582649

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

Title:
  Allow GNOME fractional scaling below 100%

Status in Mutter:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  It should be possible to scale down the whole shell to less than 100%
  e.g. 90% 85% etc.

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 16 20:14:43 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724037/+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 1434986] Re: Not working network connection after boot

[Alex]

I can confirm that this is still happening in Kubuntu 18.04. Rudolfs
Caunes's solution actually works.

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:

  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0 proto static metric 1024
   169.254.0.0/16 dev wlan0 scope link metric 1000
   192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
   eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 
Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb 
/org/freedesktop/NetworkManager/ActiveConnection/4
   wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 
/org/freedesktop/NetworkManager/ActiveConnection/3
   lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1995173] [NEW] Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue

[Yosua Liu]

Public bug reported:

The device is Lenovo Legion 7. This laptop has a mux switch to switch
between dynamic/hybrid or discrete graphics mode. This laptop has a high
resolution with high pixel density than the other displays out there,
but I don't know the exact number. Additionally, this laptop can adjust
the display refresh rate between 60 and 165 Hz.

---

There were 2 problems I encountered in dynamic/hybrid graphics mode:

- The widgets shown were too small.

Details:

The resolution was correct, at 2560x1600, but all widgets shown were too
small. I suspected this was due to the laptop screen high pixel density
and the widget size calculation didn't make use of physical dimension,
but in terms of pixel.

I thought installing NVIDIA driver would fix this, but no; this worked
in OpenSUSE Leap with KDE Plasma and I think it was because of the
inclusion of NVIDIA OpenGL driver.

The current workaround was to scale by 200% in "Display Settings",
although this make some widgets pixelated or blurred and the login
screen isn't affected by the scaling at all.

- The DE seemed to use wrong screen refresh rate.

The refresh rate I usually used is 165 Hz, but the "Display Settings"
showed 93 Hz.

Changing the refresh rate between 60 Hz and 165 Hz didn't update the 93
Hz in the "Display Settings".

OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I
think it may be either GNOME DE or xorg misconfigurations.

---

There were 3 problems I encountered in discrete graphics mode:

- The widgets were are too small.
- The DE seemed to use wrong screen refresh rate.

Details:

The above 2 problems were the same issue as encountered in the hybrid
graphics mode.

- Screen brightness was fixed at 100%.

Details:

Screen brightness could be adjusted by the keyboard fn keys, but the
brightness was fixed at 100%.

This is the most annoying problem and have forced me to use the hybrid
graphics mode which I don't like.

My first thought was a specific NVIDIA issue.

So I tried adding "acpi_backlight=vendor" and
"nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but
didn't work at all.

---

In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed
below:

Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, 
During name lookup/catalog (20210730/psobject-220)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading 
X.509 certificate -65
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)

In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above
except that there was no:

Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  520.56.06  Release 
Build  (dvs-builder@U16-T12-10-2)  Thu Oct  6 21:33:54 UTC 2022
 GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 29 18:50:17 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: nvidia/520.56.06, 5.15.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3aa6]
InstallationDate: Installed on 2022-10-29 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 82N6
ProcKernelCmdLine: 

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[elatllat]

I have not had this issue since my last comment when I disabled the
Ubuntu extentions for gnome...

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

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

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

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

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

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1724037] Re: Allow GNOME fractional scaling below 100%

[James Lewis]

I tried the suggestion in #13 to manually edit .config/monitors.xml
without success, I do hope this can eventually be realised.

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

Title:
  Allow GNOME fractional scaling below 100%

Status in Mutter:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  It should be possible to scale down the whole shell to less than 100%
  e.g. 90% 85% etc.

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 16 20:14:43 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1724037/+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 1908187] Re: Taking a screenshot during a game may lead to crash

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Taking a screenshot during a game may lead to crash

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Won't Fix
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  A screenshot of the Left 4 Dead 2 or Garry's Mod window causes the
  gnome-shell to terminate the user's session.

  [ Test case ]

  - Launch a game (Left 4 Dead 2 or Garry's Mod)
  - Open GNOME Screenshot app
  - Set "Window" in Capture Area menu and "Delay in Seconds" to 2-3 seconds
  - Alt-tab (or switch by Super key) to an open game
  - GNOME Screenshot app terminates the user session with an error "something 
went wrong".

  [ Regression potential ]

  No screenshot may be taken when requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1908187/+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 1912174] Re: gnome-shell crashed with SIGSEGV in meta_window_actor_get_meta_window() from ffi_call_unix64() from ffi_call_int() from gjs_invoke_c_function() from function_call(

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_window_actor_get_meta_window() from ffi_call_unix64() from
  ffi_call_int() from gjs_invoke_c_function() from function_call() [when
  "Minimize to Tray" extension is used]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.38.1-1ubuntu1.1, the problem page at 
https://errors.ubuntu.com/problem/2c6b4f7e8e70fd9737bcd7e6ae905e5fb99e3468 
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/gnome-shell/+bug/1912174/+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 1914225] Re: Emoji button and pack for screen keyboard

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Emoji button and pack for screen keyboard

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

Bug description:
  This enhancement requests for ubuntu default screen keyboard (compared
  to windows 10 touch keyboard, not on screen keyboard)

  I aware that ubuntu offer "insert emoji" feature but it's not usable 
everywhere and keyboard shortcut method also the same. 
https://www.omgubuntu.co.uk/2018/06/use-emoji-linux-ubuntu-apps
  Furthermore, both methods cant use as force input to any text field or any 
limited environment as if it has built-in on screen keyboard

  I noticed there're few keyboard types but its annoying to use with
  every languages. (because such keyboards are one type and our common
  language keyboards are another so always has to switch)

  Samples in two steps
  https://gitee.com/mHatsune/chaya/raw/master/disk/emoji3.jpg
  https://gitee.com/mHatsune/chaya/raw/master/disk/emoji4.jpg

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


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

[Desktop-packages] [Bug 1915066] Re: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

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

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

Bug description:
  [ Test case ]

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

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

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

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

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

  [ Regression potential ]

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

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


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

[Desktop-packages] [Bug 1914230] Re: On-screen keyboard for Japanese doesn't display Japanese characters, only English

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  On-screen keyboard for Japanese doesn't display Japanese characters,
  only English

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

Bug description:
  This is about touch keyboard.
  Screen keyboard doesn't display other languages characters, only english 
characters. I noticed many users concern about that on forums

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1914230/+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 1919972] Re: Icon grid flashes briefly before the spring animation

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Icon grid flashes briefly before the spring animation

Status in Dash to dock:
  Fix Released
Status in GNOME Shell:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  When clicking 'Show Applications', the icon grid flashes up briefly
  before vanishing again and the spring animation reveals it properly.

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


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

[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

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

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

Bug description:
  [ Impact ]

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

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

  [ Test case ]

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

  [ Regression potential ]

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

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

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


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

[Desktop-packages] [Bug 1915121] Re: gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed()
  from g_closure_invoke() from signal_emit_unlocked_R() from
  g_signal_emit_valist() from g_signal_emit()

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.38.2-1ubuntu1~20.10.1, the problem page at 
https://errors.ubuntu.com/problem/bc3566d950d42340582580239b618869c4c1d038 
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/gnome-shell/+bug/1915121/+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 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell-calendar-server assert failure on arm64: double free or
  corruption (fasttop)

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

Bug description:
  [ Impact ]

  gnome-shell-calendar-server crashes (and it seems to happen more in
  aarch64).

  https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
  https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1

  [ Test case ]

  There's not a clear test case, but this is relevant:
   - Configure a supported calendar in your online accounts 
   - GNOME shell should show your events in the calendar (under notifications 
panel)

  [ Regression potential ]

  gnome-shell-calendar-server may leak memory.

  
  ---

  M1 Mac mini
  Parallels Ubuntu VM

  ProblemType: CrashDistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic aarch64
  ApportVersion: 2.20.11-0ubuntu58
  Architecture: arm64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 17 04:34:36 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-calendar-server
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
   b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
  InstallationDate: Installed on 2021-02-17 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
  ProcCmdline: /usr/libexec/gnome-shell-calendar-server
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x81240c08 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=, p=0xe9eee300, have_lock=0) at 
malloc.c:4298
   g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: gnome-shell-calendar-server assert failure: double free or corruption 
(fasttop)
  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/gnome-shell/+bug/1915929/+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 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Cannot close the modal "Connect to Wifi" window to return to desktop

Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  When I select the task bar menu, click on the Wifi and select "Select
  to network", a modal window appears that allows me to select a Wifi
  network.

  After I have clicked on one of the networks, normally, when I click
  Cancel or Connect, the modal window disappears and returns me to the
  desktop.

  With the current gnome-shell, this modal window persists and I cannot
  access the desktop - this is both in Wayland and in X. Connect doesn't
  seem to work - it's like the buttons are no longer accepting clicks.
  The ESC key also doesn't do anything. (If I don't click on a network,
  the ESC key does work, and so does Cancel.)

  I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login
  window, but the modal window was still there when I went back into the
  desktop.

  Alt-F2 didn't work so I couldn't try re-starting gnome-shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-3ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 11 20:35:24 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1918666/+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 1921465] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_scale() from shell_blur_effect_paint() from clutter_actor_continue_paint() from clutter_paint_node_paint

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in clutter_stage_view_get_scale()
  from shell_blur_effect_paint() from clutter_actor_continue_paint()
  from clutter_paint_node_paint() from clutter_actor_paint()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.38.3-2ubuntu0.20.10.2, the problem page at 
https://errors.ubuntu.com/problem/885f3e0d59a980a433c60d937eee546b035951d3 
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/gnome-shell/+bug/1921465/+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 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell source package in Impish:
  Fix Released

Bug description:
  [Impact]

  Shell overview gets stuck where it's permanently toggled but not
  visible. Only app windows appear in their overview state. Can't
  interact with applications anymore.

  [Test Plan]

  1. Log into GNOME.
  2. Press Super+A
  3. Click on 'Files' and wait till it has launched.
  4. Press the Super key.
  Expect: Can interact with the application window.

  [Where problems could occur]

  Since the patch affects some of the core gnome-shell layout logic,
  anything is possible. Risk has been mitigated by the patch being
  small.

  [Original description]

  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu.

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922353/+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 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Regression: Onscreen Keyboard Backspace, Enter and  Capitalize do not
  work

Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully 
upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter 
and Capitalize as well as for collapsing the keyboard do not work. Pressing 
them just does nothing.
  Related logs in jouralctl output:

  
_press@resource:///org/gnome/shell/ui/keyboard.js:337:39
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22
  Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_release@resource:///org/gnome/shell/ui/keyboard.js:370:36
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22
  Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_press@resource:///org/gnome/shell/ui/keyboard.js:337:39
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22
  Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_release@resource:///org/gnome/shell/ui/keyboard.js:370:36
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22
  Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_press@resource:///org/gnome/shell/ui/keyboard.js:337:39
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22
  Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_release@resource:///org/gnome/shell/ui/keyboard.js:370:36
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22
  Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_press@resource:///org/gnome/shell/ui/keyboard.js:337:39
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22
  Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is 
out of range for uint32
  
_getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24
  
_release@resource:///org/gnome/shell/ui/keyboard.js:370:36
  
_makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1918738/+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 1922340] Re: GNOME lock screen wallpaper turns black on main display

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1922340

Title:
  GNOME lock screen wallpaper turns black on main display

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  1)
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04

  2)
  gnome-shell:
Installed: 3.38.4-1ubuntu1
Candidate: 3.38.4-1ubuntu1
Version table:
   *** 3.38.4-1ubuntu1 500
  500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  3)
  This bug only appears on Gnome with Wayland. It does not affect Gnome on xorg.

  After the screen stays off and locked for some time the wallpaper on
  the main display turns black. It never happens on the secondary
  display.

  The issue is also reported, here on gitlab:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3206

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 11:50:15 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922340/+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 1923075] Re: Unmaximizing a window by dragging is buggy

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => 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/1923075

Title:
  Unmaximizing a window by dragging is buggy

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  The unmaximize animation does not play correctly (only "slides" but
  does not "scale").

  Note that unmaximizing by using the maximize button or alt+f10 works 
correctly.
  Also X applications such as xterm unmaximize correctly when dragged off from 
the top bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  8 17:42:01 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:5024]
  InstallationDate: Installed on 2021-04-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  MachineType: LENOVO 80B6QB0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=431ba979-ee7c-490a-b2db-4996f68514e9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2013
  dmi.bios.release: 2.2
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J7ET57WW (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 80B6QB0
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 2.2
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ7ET57WW(2.02):bd11/07/2013:br2.2:efr2.2:svnLENOVO:pn80B6QB0:pvrB5400:rvnLENOVO:rn80B6QB0:rvr31900058STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: B5400
  dmi.product.name: 80B6QB0
  dmi.product.sku: LENOVO_MT_80B6
  dmi.product.version: B5400
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1923075/+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 1925683] Re: Cursor Tracking with Gnome Shell Magnifier on Wayland

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1925683

Title:
  Cursor Tracking with Gnome Shell Magnifier on Wayland

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Affected version
  GNOME 3.36 - 3.40.
  Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
  Wayland only.
  Bug summary
  When running GNOME shell with Wayland, the cursor and focus tracking 
functionality of the magnifier (a11y feature) do not correctly compute the 
cursor/focus location. The position is calculated from the top left of the 
window but the windows position is not included. This causes the magnifier to 
track the wrong location when the window is not maximiser or is on a second 
monitor.

  I suspect this is related to the way in which wayland is designed. But
  my experience in this area is minimal. When using X11 this feature
  works correctly.

  The wiki page states that under wayland the cursor and focus tracking
  work but this information is either out dated or was not tested
  correctly.

  Steps to reproduce
  From the Gnome desktop, open a terminal by pressing ctrl + alt + t or by 
opening the activities overlay and searching for "terminal".
  Press super + left arrow key to maximize the terminal window on the left side 
of the screen.
  Activity the magnifier by pressing super + alt + 8.
  Type text into the terminal window. The magnified view will move with the 
text cursor.
  Press super + right arrow key to maximize the terminal windows on the right 
side of the screen.
  Type text into the terminal. The magnified view will move but it will not 
show the text cursor. It will move when text is entered but will focus on the 
left side of the screen.
  What happened
  The magnified view does not follow the text/focus cursor correctly.

  What did you expect to happen
  The magnified view should follow the cursor and show the cursor as it does 
when the widnows is maximized. The correct behaviour can also be seen in Gnome 
shell running with X11.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  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: ubuntu:GNOME
  Date: Thu Apr 22 20:55:25 2021
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2021-04-22 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1925683/+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 1922559] Re: osk: umlauts do not work in password prompts

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1922559

Title:
  osk: umlauts do not work in password prompts

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  When I try to input a german umlaut like "ü" in a gnome-shell password
  prompt using the onscreen keyboard, nothing appears in the input
  field. In regular applications like gedit umlauts work however, so it
  seems to be specific to password prompts.

  Couldn't find anything interesting the the journalctl log, only
  messages related to gnome-shell at the time of trying to input the
  umlaut are:

  Apr 05 14:41:24 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70 
Gjs_ui_windowPreview_WindowPreview:last-child ("Loading…")] in window slots
  Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70 
Gjs_ui_windowPreview_WindowPreview:first-child ("Home")] in window slots
  Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70 
Gjs_ui_windowPreview_WindowPreview:last-child ("Home")] in window slots
  Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70 
Gjs_ui_windowPreview_WindowPreview:last-child ("Home")] in window slots
  Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70 
Gjs_ui_windowPreview_WindowPreview:last-child ("Home")] in window slots

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  Uname: Linux 5.11.11+ x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Apr  5 14:24:19 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922559/+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 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => 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/124440

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  New
Status in GTK+:
  New
Status in Mir:
  Fix Released
Status in Mutter:
  New
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+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 1926799] Re: Cursor is not rendered in the correct location when at maximum desktop zoom

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1926799

Title:
  Cursor is not rendered in the correct location when at maximum desktop
  zoom

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Affected version
  LSB Version: 
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
 
  Gnome Version: 3.38.4 
  Occurs in: Xorg and Wayland

  Bug summary

  1. zoom focus shifts - lets assume a window in the center of the
  screen and i am at 3x zoom and i try to point my mouse at something
  and try to click that. 90% of the time zoom focus shifts away from the
  mouse location to mostly top left corner of the screen.

  2. mouse pointing away from the object - Similarly when i reach above
  some zoom limit sets say 4x and now lets say i am in a browser trying
  to click a link i point at the link cursor changes to hand and when i
  try to click i couldnt. So i try to zoom out and i fid that the
  pointer was not exactly placed on the link. To sum up when zoomed in
  it seems like i am pointing at a link while the cursor is actually
  placed away from the link

  3. Compressing text - after reaching certain high zoom level as said
  4x or 5x the content on the screen becomes a bit compressed on the
  sides texts and images and everything on screen becomes elongated

  Steps to reproduce

  1. Turn on zoom from settings -> Accessibility
  2. Zoom in above 3.x
  3. Try clicking on some object inside a window
  4. Choose Follow mouse cursor or on screen part droopdown choose full screen.
  5. My current settings are Screen part: Full Screen, Magnifier cursor pushes 
content arround. However these issues persist with all the other options under 
magnifier position. Such as Follow mouse cursor or magnifier cursor pushes 
content arround or any such option provided.
  Screenshot_from_2021-05-03_14-37-09

  What happened

  1. Zoom focus shifts away from the cursor mostly towards top left of the 
window or the desktop.
  2.While zoomed in cursor seems to be placed above a link or an object but is 
actually placed awway either to the left or right of the object. Original 
position of the cursor reveals when zoomed out.
  3.Content on screen seems to be compressed from the sides as text and other 
objects appear elongated.

  I have also posted the same issue on the GNOME Community: 
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4228
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 3.38.4-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  Tags:  wayland-session hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1181666

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

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

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

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

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1532508

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 1754687] Re: gnome-shell crashes with meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashes with
  meta_monitor_manager_get_logical_monitor_from_number: assertion
  '(unsigned int) number < g_list_length (manager->logical_monitors)'
  failed

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

Bug description:
  I have a kaby lake nuc (NUC7i5BNK) connected to a Samsung 4K tv over
  hdmi. If i turn the TV off, when i switch it back on, the session is
  killed and I'm sent back to the login screen.

  Occurs on 17.10 and 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.27.92-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Fri Mar  9 15:02:50 2018
  InstallationDate: Installed on 2017-12-01 (98 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1754687/+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 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Fix Released
Status in GNOME Shell:
  Fix Released
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+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 1707831] Re: [enhancement] Replace/extend the "Activities" label with an icon/logo/glyph

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1707831

Title:
  [enhancement] Replace/extend the "Activities" label with an
  icon/logo/glyph

Status in GNOME Shell:
  New
Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Opinion
Status in yaru-theme package in Ubuntu:
  Opinion

Bug description:
  I suggest replacing the "Activities" label with the Ubuntu icon/logo.

  "Activities" sounds awkward and misleading. It would be more suitably
  vague, and more consistent with the existing Unity7 experience if the
  Gnome Shell "Activities" label was replaced by just the Ubuntu logo.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Tue Aug  1 11:28:08 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1707831/+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 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1682542

Title:
  Add support for top bars on all monitors to allow for multi-monitor
  support in primary extensions - apps-menu, places-menu, topbar, etc

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

Bug description:
  This issue will effectively be a regression in desktop usage once
  Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work
  well with multiple monitors unlike every other desktop environment
  except Budgie, which is switching away from GTK/Gnome to Qt with
  Budgie 11 due out in the next month or two.

  I reported it upstream last month but it does not appear to have much
  traction at the moment.

  https://bugzilla.gnome.org/show_bug.cgi?id=780078

  "
  It would be nice if the primary included gnome-shell extensions, eg apps-menu 
and places-menu (and by extension the topbar) supported multi-monitor similar 
to how the bottom bar 'window-list' currently does. This was easy to achieve on 
Gnome 2 and now via MATE (out of the box) but there does not appear to be any 
way to do this with Gnome 3. This also leads to there not being a way to do 
this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of 
the box than Gnome 3.

  BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so
  it is very cheap to deploy a triple head system (~ $200 for 3 1080p
  monitors). AMD supports up to quad head in their IGPs.

  This has been blocking me from moving to Gnome 3 since its release and I 
finally decided to write a bug report about it. I have had all multi-monitor 
systems since prior to 2004.
  "

  And see comments #11 and #14 from Florian.

  "
  No, you don't want that in the extensions. Each extension is separate, so 
what you are asking for here is that apps-menu and places-menu *both* add top 
bars to non-primary monitors. We are definitely not going to add two or more 
stacked panels at the top.

  What you probably want instead is an option in gnome-shell to put top bars on 
non-primary monitors, and the aforementioned extensions to handle that case.
  "

  "
  Well, we've established what you want, but that doesn't necessarily mean that 
we'll implement it.

  So far the reasoning seems to be:
   - you really want the feature
   - GNOME 2 / Windows has it

  Unlike the case of the window list, nothing in the top bar (except for
  the app menu to some extent) is tied to a particular monitor, so
  there's a much weaker case here IMHO.

  (I'll also note that this wouldn't be a "cheap" option, but require work on 
lots of details throughout the stack - we'd need to figure out the overview 
(only include the activities button on the primary monitor? or allow an 
overview on any monitor?), get API to control the brightness of a particular 
monitor (rather than the built-in one), don't use "the monitor with the top 
bar" as indicator for the primary monitor in Settings, ...)
  "

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1682542/+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 1760849] Re: Login screen appears on only one monitor and it's not the one I want

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1760849

Title:
  Login screen appears on only one monitor and it's not the one I want

Status in GNOME Shell:
  New
Status in gnome-control-center package in Ubuntu:
  Opinion
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Upstream bugs:
  https://gitlab.gnome.org/GNOME/gdm/issues/168
  https://gitlab.gnome.org/GNOME/gdm/issues/183
  https://gitlab.gnome.org/GNOME/gdm/issues/195
  https://gitlab.gnome.org/GNOME/gdm/issues/319
  https://gitlab.gnome.org/GNOME/gdm/issues/372
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3867

  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1760849/+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 1766503] Re: ibus-* randomly use high CPU

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  ibus-* randomly use high CPU

Status in GNOME Shell:
  Fix Released
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Opinion
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1766503/+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 1755779] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured_standard() from _gdk_x11_display

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_writer_default() from g_log_structured_array() from
  g_log_structured_standard() from _gdk_x11_display_error_event()
  ["BadPixmap (invalid Pixmap parameter)"] from ...
  meta_pre_paint_func()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/37a88e96048de35d02939c3dd8fe220f716448ee
  https://gitlab.gnome.org/GNOME/mutter/issues/253

  ---

  don't know why, maybe related to printer

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 10:02:43 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'libreoffice-calc.desktop', 
'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'libreoffice-writer.desktop', 'yelp.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-02-12 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1755779/+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 1778983] Re: Resume from suspend on Wayland breaks window positioning

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => 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/1778983

Title:
  Resume from suspend on Wayland breaks window positioning

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in mutter package in Fedora:
  Confirmed

Bug description:
  While on the Xorg session things seem to be mostly correct on Wayland
  after resume from suspend several things are broken:

  1) The session resumes on the 4th virtual desktop independently on where it 
was before
  2) The fullscreen virtualbox session I keep in the fourth desktop now has 
broken dimensions not covering the whole screen and/or being offset from the 
screen (a gap on the top showing the background and a covered part at the 
bottom of the screen)
  3) In what may be the same bug the terminal and gedit windows I keep tiled to 
the right and left of virtual desktop 2 show up with wrong sizes.

  To fix 2) and 3) I have to do the same thing, take the windows out of
  tiling/fullscreen and go back, so somewhere the actual state of the
  windows was lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 20:14:45 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-31 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1778983/+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 1786757] Re: Gnome Shell screencast doesn't work at desktop resolution 4880x1085

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => 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/1786757

Title:
  Gnome Shell screencast doesn't work at desktop resolution 4880x1085

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

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/263

  ---

  Ubuntu 18 shows only black output on 3 monitor display screencast. I'm using 
desktop with videocard with 3 display output (HDMI, VGA, DVI). On dual monitor, 
screecast works fine while on 3 monitors the output is only black screen.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-06-08 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1786757/+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 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => 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/108

Title:
  Desktop briefly becomes unresponsive when receiving a keypress from a
  different device/mapping than the last keypress (in Xorg)

Status in GNOME Shell:
  Fix Released
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1823616] Re: Incorrect date format for Australia

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Incorrect date format for Australia

Status in GNOME Shell:
  New
Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  The calendar in the menu bar of gnome-shell is not adhering to the
  localisation settings for Australia. The issue is displayed both in
  the menu bar date and within the calendar popout as well. The
  localisation configuration in the Settings appears to display
  correctly whilst the calendar in the menu bar is showing US layout.
  This issue appears in a minimal install of the OS. I have not tested
  the behaviour in a full install.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 15:42:35 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1823616/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

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

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1850995] Re: Hang when interacting with desktop icons on X11

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Hang when interacting with desktop icons on X11

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  It's easy to reproduce: Put files on the desktop, select them, the selection 
remains and the whole shell crashes.
  I switch to a tty2 session and see the gnome-shell process with 100% CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  2 00:32:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-18 (256 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
  RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1850995/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym...

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Window manager warning: Overwriting existing binding of keysym...

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

Bug description:
  1) Ubuntu 19.10
  2) Gnome 3.34.1
  3) No error.
  4) Error in Ubuntu Logs App.

  Sender: gnome-shell
  Message:
  4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 
GMT-0600 (CST)
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 37 with keysym 37 (keycode 10).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 36 with keysym 36 (keycode f).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 35 with keysym 35 (keycode e).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 34 with keysym 34 (keycode d).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 32 with keysym 32 (keycode b).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 39 with keysym 39 (keycode 12).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 33 with keysym 33 (keycode c).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 38 with keysym 38 (keycode 11).
  4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding 
of keysym 31 with keysym 31 (keycode a).
  Audit Session: 2
  Priority: 6

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1868293] Re: gnome-shell crashed in meta_workspace_index: Workspace does not exist to index!

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1868293

Title:
  gnome-shell crashed in meta_workspace_index: Workspace does not exist
  to index!

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

Bug description:
  https://errors.ubuntu.com/problem/5340b1db97f4c8202e6c7a695097f4f6c22a0695

  ---

  gnome-shell crashed when I tried to move fireforx from one workspace
  to another.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 18:49:14 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-03-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_bug () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   meta_workspace_index () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /lib/x86_64-linux-gnu/libffi.so.7
   () at /lib/x86_64-linux-gnu/libffi.so.7
   () at /lib/libgjs.so.0
  Title: gnome-shell crashed with SIGABRT in meta_bug()
  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/gnome-shell/+bug/1868293/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
  OpenGL app windows

Status in Mutter:
  Fix Released
Status in metacity package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Won't Fix

Bug description:
  Nvidia driver causes Xorg to use 100% CPU and shows high lag and
  stutter... but only when dragging glxgears/glxheads, or any window
  over them. Other apps do not exhibit the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 24 19:11:15 2018
  InstallationDate: Installed on 2018-05-26 (151 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1799679/+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 1870597] Re: libinput says "your system is too slow"

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  libinput says "your system is too slow"

Status in GNOME Shell:
  Fix Released
Status in libinput:
  Fix Released
Status in Linux:
  Confirmed
Status in libinput package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:

  During the freeze, the output of the install had a message from "gdm-
  x-session" saying "your system is too slow".

  To reproduce:
  1. Launch the Ubuntu installer
  2. Begin the installation process
  3. When the installation process begins, move the cursor around
  4. Notice how the PC freezes and drops mouse events

  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04

  gnome-shell:
Installed: 3.36.0-2ubuntu2
Candidate: 3.36.0-2ubuntu2
Version table:
   *** 3.36.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.442
  Date: Fri Apr 3 14:24:21 2020
  DisplayManager: gdm3
  GsettingsChanges:

  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1870597/+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 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

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

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1876632

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

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

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  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 

[Desktop-packages] [Bug 1873625] Re: Center the mouse cursor at startup

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Center the mouse cursor at startup

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When I open a session, the mouse cursor moves at the bottom-right of
  the screen, at a fixed position. The coordinates are about (x:1730,
  y:970) on a 1920x1080 screen.

  When I close the session, the mouse goes again to this position.

  I am not sure if the issue really comes from mutter, or gdm, or other
  component.

  This behavior is specially annoying because your first action after
  log-in will probably consist in launching an application by clicking
  its icon at opposite position of the screen, in the top-left part of
  the launch bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 09:03:01 2020
  InstallationDate: Installed on 2018-04-07 (742 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-04-04 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1873625/+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 1870822] Re: gnome-shell crashed with assertion failure window.c:1552:meta_window_unmanage: assertion failed: (window->display->focus_window != window)

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with assertion failure
  window.c:1552:meta_window_unmanage: assertion failed:
  (window->display->focus_window != window)

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  The gnome user interface hung for a minute or so, after pressing 'x'
  to close a terminal window

  [ Test case ]

  - Run wine on wayland (natively) 
  - Open a window containing a dialog box
  - Close the dialog

  Otherwise

  - Closing a terminal should work

  [ Regression potential ]

  Windows are wrongly focused on click.


  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:40:19 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-03 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT
  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/mutter/+bug/1870822/+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 1880218] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_background_image_shadow() from st_theme_node_paint_equal() from st_widget_

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from
  st_theme_node_get_background_image_shadow() from
  st_theme_node_paint_equal() from st_widget_recompute_style() from
  st_widget_style_changed()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.36.2-1ubuntu1~20.04.1, the problem page at 
https://errors.ubuntu.com/problem/1918c0de443d58d0513f9914a411daf2c41bdad6 
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/gnome-shell/+bug/1880218/+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 1878293] Re: xterm resize is wonky

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  xterm resize is wonky

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in xterm package in Ubuntu:
  Invalid
Status in mutter source package in Groovy:
  Fix Released
Status in xterm source package in Groovy:
  Invalid
Status in mutter source package in Hirsute:
  Fix Released
Status in xterm source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]

  When I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  [ Test case ]

  - Start Xterm
  - Resize the window from its top/left corner
  - It should resize normally, and not act as shown in

https://gitlab.gnome.org/GNOME/mutter/uploads/3c19763b7748ce76b0ba2958cde7636b/Screencast_from_02-04-19_14_03_24.webm

  [ Regression potential ]

  Windows resizing might not work correctly

  ---

  % lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal

  % wmctrl -m
  Name: GNOME Shell
  Class: N/A
  PID: N/A
  Window manager's "showing the desktop" mode: OFF

  Terms:
  window has four sides: top, bottom, left, and right
  when referring to corners, "upper" means "top", and "lower" means "bottom",
  so the four corners are upper-right, lower-right, lower-left, and  upper-left.
  wonky: works wrong, as detailed below ("cases that work wrong...")

  Description:

  I can resize a gnome-terminal window, everything works fine.
  (Grab it, using the mouse, by the upper-right corner (click-and-hold);
  the size changes as the mouse is moved, because the position
  of the upper-right corner follows the mouse.  (Only the upper-right corner 
moves.))
  But when I try to resize an xterm window the same way,
  this happens instead: as the mouse is moved, the upper-right corner
  does move, but it doesn't track with the mouse pointer like it should.
  Meanwhile, the lower-left corner also moves (it should have remained anchored 
in its original x-y position on the screen).

  Cases that work correctly:
  If the xterm window is grabbed by the lower-right corner and resized, this 
case works properly.
  If the xterm window is grabbed by the bottom edge and resized, this case 
works properly.
  If the xterm window is grabbed by the right edge and resized, this case works 
properly.

  Cases that work wrong ("wonky"):
  If the xterm window is grabbed by the left edge and resized, then the 
opposite (i.e. right) edge (incorrectly) migrates.
  If the xterm window is grabbed by the top edge and resized, then the opposite 
(i.e. bottom) edge (incorrectly) migrates.
  If the xterm window is grabbed by the upper-right corner and resized, then 
the window (incorrectly) migrates.
  If the xterm window is grabbed by the lower-left corner and resized, then the 
window (incorrectly) migrates.
  If the xterm window is grabbed by the upper-left corner and resized, then the 
window (incorrectly) migrates.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xterm 353-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01: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: GNOME
  Date: Tue May 12 13:52:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: PNY GK107 [GeForce GT 740] [196e:109a]
  InstallationDate: Installed on 2020-05-06 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7f55a3c5-bff9-45ea-8979-583e4fbfec07 ro quiet splash 
vt.handoff=7SourcePackage: xterm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  

[Desktop-packages] [Bug 1871262] Re: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => 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/1871262

Title:
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

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

Bug description:
  GNOME Shell-Message: 20:18:17.677: Telepathy is not available, chat 
integration will be disabled.
  Gjs-Message: 20:18:18.189: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1028]: 
unreachable code after return statement
  Ubuntu AppIndicators-Message: 20:18:19.456: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.79/org/ayatana/NotificationItem/software_update_available
  Ubuntu AppIndicators-Message: 20:18:19.461: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem :1.79/org/ayatana/NotificationItem/livepatch
  GNOME Shell-Message: 20:18:19.742: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation

  (gnome-shell:21601): mutter-CRITICAL **: 20:18:45.274:
  meta_window_set_stack_position_no_sync: assertion
  'window->stack_position >= 0' failed

  Was the error I got after restarting Gnome after it froze when I
  closed Visual Studio Code but the right-click menu appeared for it
  after Ubuntu froze for a second because I had regions enabled on my
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Mon Apr  6 20:16:51 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (2 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2020-04-04 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1871262/+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 1882462] Re: Displays wake up pre-maturely (likely driven by notification)

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Displays wake up pre-maturely (likely driven by notification)

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After a period of time, my displays go to sleep as they should.
  However, I often come back to find that the displays are awake, the
  mouse pointer is on a screen, but the screens are otherwise black.
  They're in this weird "awake but not fully on" mode. At that point,
  they will not go back to sleep as they should unless I fully awake
  them and let them go back to sleep.

  I don't know exactly what triggers the "half awake" but I suspect it's
  a notification. The displays shouldn't turn on without a user action.
  It wastes power and is clearly broken. I've attached a photo for an
  example.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 16:10:20 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (684 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1882462/+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 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions)

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions)

Status in GNOME Shell:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1896627/+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 1883130] Re: AppIndicator icons overlay the clock in the panel

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  AppIndicator icons overlay the clock in the panel

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Triaged

Bug description:
  When I open some apps, some of them displays a top bar icon. At some
  point, there is so many icons than they overlay the clock, as shown in
  attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 11 11:54:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:139d]
  InstallationDate: Installed on 2020-05-26 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. S451LA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=85895dc0-0f4c-4998-9659-78a68fab28cd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S451LA.403
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: S451LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrS451LA.403:bd01/17/2014:svnASUSTeKCOMPUTERINC.:pnS451LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS451LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: S
  dmi.product.name: S451LA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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-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/1883130/+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 1887296] Re: Moving popup windows drags the application's main window behind it

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1887296

Title:
  Moving popup windows drags the application's main window behind it

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Sometimes programs open a "popup" or a "secondary", "child" window, I
  don't know what the word is.

  For example, in Chrome, if I right-click on an image in a web page and
  choose "Save As", this will open a new file browser window that allows
  me to browse for a directory to save the image to.

  Until Ubuntu 16.04, I could move that child window around by dragging
  it by its title bar, and that would not move around the parent window
  behind it.

  Now, it does. That is, the "parent" window greyes out, and moving the
  "child" window (i.e. the popup) on the foreground causes the parent
  window in the background to move as if they were glued together.

  In the above example, if I drag around the "Save As" window, the
  Chrome window behind it moves too. Even worse, if the parent window is
  maximized, it will "oppose resistance" to the dragging of the popup
  window, and if I drag far enough, the parent window will unmaximize
  and unblock the movement of both windows.

  It's pure madness.

  
  I can't imagine a scenario where this is the unavoidable consequence of some 
improvement. It looks like it is by design.

  Why?

  What were you thinking? Why do you ACTIVELY work to degrade usability
  and make the users' life miserable??

  
  Here's a very real-life example:

  As mentioned above, I right-click on something in the browser (like an
  image or a video) and do Save As. When the file browser window opens,
  it covers the content of the web page from which I was saving the
  content. Maybe I want to move the child window in order to reveal the
  web page that I was visiting in the first place, because the context
  (which I haven't memorized in full in my brain just yet) helps me
  choose a file name for the very file I'm saving.

  
  Another example: I am browsing some folder in Nautilus. I right-click on a 
file or folder inside it, and open Properties. That opens in a popup. Now I 
want to have another look at the name of the file I selected (of which I'm now 
seeing the properties), and those around it, because I'm wondering if I chose 
the wrong file, or for whatever other reason. I can't do taht without closing 
the Properties window.

  The everyday examples are countless.

  
  This is idiotic. Seriously, what are you doing?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 18:11:28 2020
  DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit()
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108: added
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 

[Desktop-packages] [Bug 1898393] Re: Gnome 3.38 Magnifier does track mouse cursor.

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Gnome 3.38 Magnifier does track mouse cursor.

Status in gjs:
  Fix Released
Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  The mouse tracking when using the Gnome shell magnifier doesn't work.
  Text cursor and focus cursor tracking works fine.

  To re-poroduce enable the magnification by pressing Super + Alt + 8.
  Move the mouse around and observe the magnified view remaining in one
  place. The magnified view should follow the mouse cursor.

  Tested on both X and Wayland. Using a virtual machine and Dell XPS
  9630.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  3 21:22:21 2020
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.a11y.applications' b'screen-magnifier-enabled' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['update-manager']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2020-10-03 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1898393/+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 1896190] Re: Airplane mode hotkey(F8) is useless while open pop-menu

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1896190

Title:
  Airplane mode hotkey(F8) is useless while open pop-menu

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On 20.04 ubuntu, click the top right tray bar to open the menu, or
  right click at terminal to show a popup menu, then press F8 to
  enable/disable Airplane Mode, it doesn't work.

  But the Brightness(F5/F6) or Volume(F3/F4) works fine.

  ThinkPad series, such as ThinkPad L15, ThinkPad X13, ThinkPad T14s, I
  believe it's a general issue on latest Thinkpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1896190/+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 1895941] Re: Screen lock after some minutes while playing vidoes from mpv player.

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => 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/1895941

Title:
  Screen lock after some minutes while playing vidoes from mpv player.

Status in Mutter:
  New
Status in mpv package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I installed mpv player from APT repository.
  It was working fine but from last week I have been experiencing this issue.
  The issue is: Screen gets locked while watching video.

  Normally, this should not have happened. But something has gone wrong.
  Video continue to play in background but to watch it I need to unlock the 
screen.I was using wayland when this problem started..

  
  Something is triggering to lock the screen while playing any movies/videos, 
which is very weird.
  Let me know if you need more output to resolve this issue.

  suraj@surtoshwi ~> mpv --version
  mpv 0.32.0 Copyright © 2000-2020 mpv/MPlayer/mplayer2 projects
   built on UNKNOWN
  ffmpeg library versions:
     libavutil   56.31.100
     libavcodec  58.54.100
     libavformat 58.29.100
     libswscale  5.5.100
     libavfilter 7.57.100
     libswresample   3.5.100
  ffmpeg version: 4.2.4-1ubuntu0.1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mpv 0.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 17 13:18:02 2020
  InstallationDate: Installed on 2020-04-24 (145 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: mpv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1895941/+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 1901391] Re: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement)

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Ctrl+Alt+Shift+R screen recording not working anymore in 20.10
  (Pipewire is now a requirement)

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  I'm using gnome-shell with wayland (don't know if that matters), and,
  when I press CTRL-ALT-SHIFT-R, nothing happens. I checked my keyboard
  shortcuts, and this shortcut is supposed to trigger screencasting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Oct 25 10:39:48 2020
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-07 (260 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1901391/+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 1901016] Re: APP GRID TOO LARGE

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1901016

Title:
  APP GRID TOO LARGE

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  When you click on the app button, the icons in the app grid shown is
  way too large.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 22 13:11:04 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2020-10-03 (18 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   LANGUAGE=en_NG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NG
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=9f6d2f48-a8cd-464f-8ea4-11fec7ad9369 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-focal
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-focal
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1901016/+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 1902829] Re: Missing "Mobile Broadband" menu item

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Missing "Mobile Broadband" menu item

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

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1902829/+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 1905330] Re: Backport Wayland frame callback fix for 3.28 for Firefox testing infrastructure

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Backport Wayland frame callback fix for 3.28 for Firefox testing
  infrastructure

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released
Status in mutter source package in Hirsute:
  Fix Released

Bug description:
  The Firefox testing infrastructure is based on Ubuntu 18.04. In order
  to enable the Wayland backend by default, we need to also run test on
  that.

  There is one particular bug in Mutter 3.28 that I'd like to see fixed
  for that, thus requesting a backport of a patch. It's already in the
  upstream repo, but as 3.28 is not supported upstream any more, I
  request it here explicitly:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1570

  @vanvugt @3v1n0 this would be super helpful for us, I hope I can
  convince you about that, even if Ubuntu 18.04 doesn't support Wayland
  officially.

  It can be tested by running Firefox with `MOZ_ENABLE_WAYLAND=1` and
  setting `widget.wayland_vsync.enabled:1` in the config (soon to be
  enabled by default). If, after launching Firefox again, everything
  works as expected - well, then it works.

  Bonus: the patch also affects a number of other Wayland applications,
  so some users might be happy to see it as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1905330/+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 1903224] Re: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1903224

Title:
  Pressing the launch terminal shortcut in activities view launches two
  terminals instead of one when CTRL modifier is used

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Package: Xorg or Gnome, not really sure.

  Problem description:
  1. I have set the Launch terminal shortcut in Settings/Keyboard shortcuts to 
CTRL+`.
  2. I invoke the activities overview by pressing SUPER once. 
  3. I launch a terminal by pressing the newly set CTRL+` shortcut.

  What happened: two new terminal windows appeared.
  What is expected: launch only one terminal window.

  More info:
  This only happens when a CTRL modifier is used and the key is set to a non 
function (F1-F12) key. When an ALT or CTRL+ALT shortcut is used, only one 
window appears, as expected. 

  Expected behaviour: launch only one terminal window while in the activities 
overview.
  What happened: two new terminal windows appeared in the activities overview.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1903224/+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 1903542] Re: Ubuntu 20.10 2-in-1 regression (auto-rotate and on-screen keyboard disabled)

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1903542

Title:
  Ubuntu 20.10  2-in-1 regression (auto-rotate and on-screen keyboard
  disabled)

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  I have a 2-in-1 laptop (HP Spectre Folio) 
  With 20.04 my screen autorotated and I got a on-screen-keyboard. No it 
doesn't. So my laptop is no longer a 2-in-1 with Ubuntu. That's a serious 
regression.

  As far as I can tell this is a Gnome bug: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3255
  with a solution, but it needs to be resolved in Ubuntu 20.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1903542/+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 1906087] Re: Half of the date-time text is hidden in the calendar popover when using Tamil (India) as the language

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1906087

Title:
  Half of the date-time text is hidden in the calendar popover when
  using Tamil (India) as the language

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

Bug description:
  I am using Tamil(india) as the date-time language from Ubuntu 19. But
  after upgrading to Ubuntu 20, the date-time is half-hidden (see
  attachments).

  before upgrade it was working fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 28 10:47:42 2020
  DistUpgraded: 2020-06-06 18:27:37,926 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0792]
  InstallationDate: Installed on 2018-11-04 (755 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Vostro 14-3468
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=6272611c-ab7e-4b80-86ed-8e7dbe8d5396 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-06 (174 days ago)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 05/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.0
  dmi.board.name: 0T1X3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.0:bd05/15/2018:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 14-3468
  dmi.product.sku: 0792
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/1906087/+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 1911921] Re: auto-move-windows extension crashes gnome-shell with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  auto-move-windows extension crashes gnome-shell with SIGABRT in
  src/core/workspace.c:375:meta_workspace_add_window: assertion failed:
  (g_list_find (workspace->mru_list, window) == NULL)

Status in Mutter:
  Fix Released
Status in gnome-shell-extensions package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes when auto-move-windows extension is used with
  windows that want to be on all workspaces (like Chrome PiP).

  https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97
  https://gitlab.gnome.org/GNOME/mutter/-/issues/992

  [Test Plan]

  1. Install gnome-shell-extensions

  2. Open the 'Extensions' app and enable auto-move-windows.

  3. Configure auto-move-windows with a rule for Chrome/Chromium.

  4. Open Chrome/Chromium and point it at a simple video like from
  https://download.blender.org/peach/bigbuckbunny_movies/ or
  https://download.blender.org/demo/movies/BBB/

  5. Set the Chrome tab playing the video to PiP mode.

  Expect: No crashes and the video moves to an external window.

  [Where problems could occur]

  Changing mutter's window management code always brings risk of
  regression to the GNOME desktop.

  [Other Info]

  As in bug 1864052, putting a Chrome video into PiP mode crashes gnome-
  shell, although this time, in a different location.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6
  Uname: Linux 5.10.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jan 15 16:04:30 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-03-14 (1037 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-7.so.0
   () at /lib/x86_64-linux-gnu/libmutter-7.so.0
   meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1911921/+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 1929650] Re: Screen doesn't turn off when using Wayland on some devices

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  Screen doesn't turn off when using Wayland on some devices

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When the screen of my laptop (Thinkpad E480) is supposed to turn off
  (because of inactivity or when actively locking screen), the screen
  dims, turns off for a second and then turns back on while remaining
  dimmed. I can see the backlight of the screen and the cursor.

  This bug is only present when using a wayland-session regardless of my
  settings. It also happens with a fresh user account. Additionally, I
  tested with the 5.8 and 5.12 kernels with the same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-power-manager 3.32.0-2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 26 08:13:27 2021
  InstallationDate: Installed on 2021-05-24 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1929650/+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 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_place() from
  place_window_if_needed() from meta_window_constrain() from
  meta_window_move_resize_internal() from meta_window_force_placement()

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Confirmed
Status in mutter package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.38.4-1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 
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/mutter/+bug/1933186/+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 1929773] Re: gnome-shell says: JS ERROR: TypeError: method Gio.File.delete_async: At least 3 arguments required, but only 2 passed

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell says: JS ERROR: TypeError: method Gio.File.delete_async:
  At least 3 arguments required, but only 2 passed

Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  Fix Released
Status in gjs source package in Impish:
  Fix Released

Bug description:
  I keep seeing this in hirsute logs in various bug reports:

  gnome-shell[1505]: JS ERROR: TypeError: method Gio.File.delete_async: At 
least 3 arguments required, but only 2 passed
   
_handleLockScreenWarning@resource:///org/gnome/shell/ui/main.js:323:24
   
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:303:13
   
_startupAnimationComplete@resource:///org/gnome/shell/ui/layout.js:733:14
   
onComplete@resource:///org/gnome/shell/ui/layout.js:711:36
   
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13
   
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1929773/+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 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1930371

Title:
  top bar displayed on top of a fullscreen window that gets moved from
  one monitor to another

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  I have two monitors: the laptop's internal one (primary), and an
  external LCD positioned above the it.

  I have configured mpv to be the default video player in Nautilus.  I
  have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'.

  Steps to reproduce:
  - click on a video file in Nautilus
  - mpv is launches in fullscreen mode on the external monitor
  - drag the mpv window with the mouse to the internal monitor

  Expected behavior:
  - mpv is fullscreen on the internal monitor

  Actual behavior
  - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the 
video

  Workaround: hit  twice.

  Alternative workaround: alt-tab so a different window is on top of mpv
  then alt-tab back.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  1 10:02:15 2021
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (719 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1930371/+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 1934458] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  on_window_icon_changed() from g_closure_invoke() from
  signal_emit_unlocked_R() from g_signal_emit_valist() from
  g_signal_emit() from g_object_dispatch_properties_changed() from
  g_object_notify_queue_thaw() from g_object_thaw_notify() from
  meta_window_update_icon_now() from idle_update_icon()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.38.4-1ubuntu3~21.04.1, the problem page at 
https://errors.ubuntu.com/problem/29945d56fd6502de24678bddb8f825c97977fcbb 
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/gnome-shell/+bug/1934458/+subscriptions


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

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

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

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

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

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

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


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

[Desktop-packages] [Bug 1937854] Re: Keyboard shortcut Super+Alt+Up is hardcoded to show activities overview

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1937854

Title:
  Keyboard shortcut Super+Alt+Up is hardcoded to show activities
  overview

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  ### Affected version

  Ubuntu 21.10 (dev), Wayland, Gnome 40.2.0, gnome-shell 40.2-1ubuntu1

  ### Bug summary

  The keyboard shortcut `Super+Alt+Up` seems to be hardcoded to
  something along the lines of showing activities overview, and cannot
  be removed or used for any other action, even if it's shown as
  assigned to one.

  ### Steps to reproduce

  1. Open system preferences, and navigate to Keyboard -> Keyboard Shortcuts -> 
Customize Shortcuts -> System
  2. Verify that no action has `Super+Alt+Up` set, removing/changing any 
actions if it's already assigned.
  3. Optional: assign `Super+Alt+Up` to some other action.
  4. Press `Super+Alt+Up`

  ### What did you expect to happen

  Either the action which `Super+Alt+Up` is shown to be assigned to, or
  nothing if no action has that shortcut assigned.

  ### What happened

  The activities overview is shown.

  ### Upstream bug report

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4497 - maintainers
  indicated this is most likely cause by a downstream modification.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 23 12:54:57 2021
  DisplayManager: gdm3
  GsettingsChanges:

  InstallationDate: Installed on 2019-11-17 (614 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

  _Edit: fix `Super+Up`-> `Super+Alt+Up`_

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1937854/+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 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Alt-tab stops switching windows [JS ERROR: TypeError: window is null
  _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When a new Wayland session is created from a login, Alt-tab works as
  expected to change windows.  After sometime Alt-tab fails to do
  anything (super-tab still works to change applications) and the
  following error is created in syslog:

  gnome-shell[18]: JS ERROR: TypeError: window is
  
null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24

  The only workaround I have found is to logout and log back in, however
  after some time the error repeats itself.

  Ubuntu 21.04
  gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 10:53:32 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-11-11 (230 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago)

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


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

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

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1936703

Title:
  screen keyboard doesn't work on authentication window

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

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

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

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


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

[Desktop-packages] [Bug 1933799] Re: gnome-shell crashed with SIGSEGV in rescan_icon_theme() from installed_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist()

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1933799

Title:
  gnome-shell crashed with SIGSEGV in rescan_icon_theme() from
  installed_changed() from g_closure_invoke() from
  signal_emit_unlocked_R() from g_signal_emit_valist()

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.38.4-1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/0743486472675f657b0ac6603c8e0fda941d5c40 
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/gnome-shell/+bug/1933799/+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 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange
  circle persists

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Running 21.10 and Gnome 40.4 the screen recording no longer works with
  the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
  folder but it is empty. The orange circle does appear in the upper
  corner, but it will not go away.

  Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or
  remove the orange circle.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:11:13 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1948647/+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 1937958] Re: gnome-shell gdb instructions cause immediate "Oh no" crash

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell gdb instructions cause immediate "Oh no" crash

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  I wanted to report a gnome-shell bug with a backtrace, so tried to use
  the instructions in

     https://wiki.gnome.org/Projects/GnomeShell/Debugging

  which say to do the following in an ssh login or separate VT:

    gnome_session=$(pgrep -u $USER gnome-session)
    eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep 
DISPLAY)
    eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep 
XAUTHORITY)
    eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep 
DBUS_SESSION_BUS_ADDRESS)
    gdb
    ...etc...

  However three problems came up, two minor (wrong instructions), the
  other major:

  (1) There is more than one gnome-session process, and so the shell
  variable $gnome_session gets set to a list of several PIDs, which in
  turn causes syntax errors when using the expression
  "/proc/$gnome_session/environ".

  In Ubuntu 21.04 I have three gnome-session processes immediately after
  rebooting and logging in (I have auto-login enabled, so the login
  happens by itself, in case that matters):

  $ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/')
  UID  PIDPPID  CSZ   RSS PSR STIME TTY  TIME CMD
  jima97439725  0 55216 16084   2 13:41 tty3 00:00:00 
/usr/libexec/gnome-session-binary --systemd --session=ubuntu
  jima98288066  0 24031  6148   8 13:41 ?00:00:00 
/usr/libexec/gnome-session-ctl --monitor
  jima98388066  0 129272 18176  7 13:41 ?00:00:00 
/usr/libexec/gnome-session-binary --systemd-service --session=ubuntu

  (2) The instructions specify this gdb command:

    call gjs_dumpstack ()

  However that results in an error and the call is not made:
  'gjs_dumpstack' has unknown return type; cast the call to its declared
  return type

  (3) Most importantly, a crash:  Immediately upon starting the new
  gnome-shell process (with option --replace) a white screen appears
  with "Oh No... something went wrong..." forcing me log out.

  The crash happens whether using an independent VT or an ssh login.

  Afterwards I typed Control-C to get control in gdb, and produced the
  attached backtraces but they don't seem useful (see attached
  typescript file).

  /var/syslog might be useful.  I will attach the portion beginning just
  before starting the new gnome-shell

  The attached typescript file shows what I did to circumvent the buggy
  instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging

  P.S. The original crash I wanted to report was that opening any .jpg
  in gimp and selecting part of the image and then doing Select->Invert
  instantly freezes the system.  The only recovery is to use a separate
  VT to kill the gimp process, after which gnome-shell restarts.  A
  system error dialog appears saying gnome-session [correction: gnome-
  shell] got a segfault somewhere; thus the desire to get a backtrace.
  But this bug report is _not_ about that bug, but is about how using
  the debug instructions in the wiki are incorrect and when fixed seem
  to cause a crash on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Sun Jul 25 13:41:54 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-07-20 (5 days ago)
  InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 
(20210421)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1937958/+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 1938988] Re: Glitches in Gnome Shell Windows

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1938988

Title:
  Glitches in Gnome Shell Windows

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I'm facing an issue in Ubuntu 21.04 with Gnome 3.38. Basically, some parts of 
the windows glitches. From my experience I think this parts are mostly the 
"updating" ones (animated icons or buttons, typing cursors etc).
  I noticed also this common behaviors in all them:

  1. It happens regardless of shell or applications theme.
  2. It only happens if there are no other open windows behind the window in 
use (or if they are running in background but minimized).
  3. It doesn't happen if there are windows behind.
  4. It disappears by moving, maximizing, minimizing or resizing the window in 
use.
  5. It doesn't happen on all applications (I tested that this happens with all 
Gnome Apps, OBS, Telegram, VLC, but not Spotify, Chrome, Olive Video Editor).

  I don't really know how to describe what I see, so here's a brief
  video I did to show and explain it. Hoping it will help. (Here's also
  a link to the same video uploaded on YouTube, not listed so it's not
  public. https://youtu.be/CRE4-49wMTo If you want to see it in HD here
  you can - sorry for resolution but my PC has 1366x768 monitor so
  highest resolution on YT is only 720).

  P.S.: I face this issue in both Xorg and Wayland, so honestly I don't
  really know if this bugs are related to Gnome Shell or Mutter.

  My PC specifications in case you need them:
  Laptop Acer A315-21-90VF
  Cpu AMD A9 with internal Radeon R5 Graphics
  1TB SSD Sata
  12GB Ram DDR4

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  5 09:13:53 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-03-10 (147 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-08-03 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1938988/+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 1936826] Re: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199]

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1936826

Title:
  gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  [st-focus-manager.c:199]

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae

  ---

  Testing daily Ubuntu Impish ISO 2021-07-19

  Test machine : Dell [Latitude] 7280 (i5-7300U,

  Received the error message - Ubuntu has experienced an internal error
  ...do you want to send ...etc, etc.

  This bug occurred when I was scrolling up and down on the "Settings"
  app and selected "Appearance".

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 19 12:15:54 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2021-07-19 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
  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/gnome-shell/+bug/1936826/+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 1943558] Re: Regression: Gnome shell has red tint after installation of Nvidia proprietary drivers

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1943558

Title:
  Regression: Gnome shell has red tint after installation of Nvidia
  proprietary drivers

Status in GNOME Shell:
  New
Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  Upstream report of this issue: https://gitlab.gnome.org/GNOME/gnome-
  shell/-/issues/4071

  A colleague tested the latest daily of Ubuntu 21.10 and had a red tint after 
installing the proprietary nvidia drivers. Did not happen with gnome-shell 
versions < 40.
  Changing display refresh rate made the red tint go away.

  This report should serve as a reminder to fix this bug before it hits the 
masses after release.
  If you need more specific info I'll request it from my colleague, he did not 
want to bother reporting the bug himself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1943558/+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 1942655] Re: Minimized windows stay ghosted on the background wallpaper

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1942655

Title:
  Minimized windows stay ghosted on the background wallpaper

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Hello, the problem that I am presented with is basic, but quite annoying.
  At any time without any type of pattern, when minimizing a window (of any 
program), these remain as "background", and become part of the wallpaper. You 
do not interact with it but it remains static on the site.
  I attach an example.
  The only temporary solution that has worked for me is to log out, but it 
almost certainly happens again.
  I appreciate the help :)
  (The theme has nothing to do with it, it happens to me even though it is 
stock)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  3 17:12:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-28 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1942655/+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 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch inpu

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  [wayland] gnome-shell elements (dock, top bar, on-screen keyboard)
  becomes unresponsive to touch / mouse while windows & desktop are
  still responsive to touch input

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Further detailed information filed in gnome-shell bug filing:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4508#note_1213365

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 28 17:56:57 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-07-15 (13 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1938352/+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 1947315] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_pa

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from
  st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow()
  from st_theme_node_get_paint_box() from
  st_theme_node_transition_get_paint_box()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
40.5-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/9e0eb2f488ad83e41a8977709955a661857ba95e 
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/gnome-shell/+bug/1947315/+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