date:20190805

top on 4 second intervals rotates the same 5 or 6 threads, so I set the
interval to 20 seconds and copied the output to a file, which I have
attached. I have also attached the dpkg list.

** Attachment added: "top interval 20 seconds"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281100/+files/schizo-2019-08-06-top-d-20

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

dpkg list next...

** Attachment added: "dpkg list"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281101/+files/schizo-2019-08-06-allpackages-txt

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

Hi Daniel, thanks for not giving up! First, here is snap list:-

Name  Version Rev   Tracking  Publisher   
Notes
core  16-2.39.3   7270  stablecanonical✓  
core
core18201907231074  stablecanonical✓  
base
gnome-3-26-1604   3.26.0.20190705 90stable/…  canonical✓  -
gnome-3-28-1804   3.28.0-10-gaa70833.aa70833  67stablecanonical✓  -
gnome-calculator  3.32.1  406   stable/…  canonical✓  -
gnome-characters  v3.32.1+git2.3367201296   stable/…  canonical✓  -
gnome-logs3.32.0-4-ge8f3f37ca861stable/…  canonical✓  -
gnome-system-monitor  3.32.1-3-g0ea89b4922100   stable/…  canonical✓  -
gtk-common-themes 0.1-22-gab0a26b 1313  stable/…  canonical✓  -
pdftk-smoser  2.02-4  18stablesmoser  -

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

Just a couple of ideas:

* Please run 'top' and tell us if any process is using high CPU while
the problem occurs.

* Please run 'snap list' and paste the output here.

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

Please also run:

  dpkg -l > allpackages.txt

and attach the file 'allpackages.txt'.

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

What can I do to help you diagnose the problem further, Daniel?

I think something changed recently, and that must have been an update. I
do not believe I have installed any new packages that might have called
for GTK2, so my guess is that it has been there since the clean 18.10
install and not been in conflict with GTK3 until recently.

Searching on the conflict has not revealed anything helpful to me
because this kind of error has popped up lots of times as far back as
ubuntu 12.04. The packages recommended to be installed to "fix" these
old problems all seem to be present on my system already.

Is there an easy way to discover what is calling for GTK2, or is that
being done by canberra on behalf of some applications, but not others?

Is there any point in me booting recovery mode to see whether the errors
(keyboard mapping too, don't forget) are logged from the simple tty
console login?

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839016] Re: Suspend is iterrupted by ALT key

I'm not familiar with the code that does suspension so suggest:

1. Verify the bug is still in Ubuntu 19.04/19.10.

2. If so then please report it to the upstream developers at:

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

   and then tell us the new bug ID.

** Tags added: bionic

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

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

Title:
  Suspend is iterrupted by ALT key

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1827428] Re: Mouse cursor left frozen copy of itself

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

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

** Summary changed:

- Mouse cursor left frozen copy of itself
+ [nvidia] Mouse cursor left frozen copy of itself

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [nvidia] Mouse cursor left frozen copy of itself

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

Thanks again. Life is rarely simple enough to reveal the cause of a
shell bug in the log. If it was though, then the canberra errors are the
only ones I think could be relevant.

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

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

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839008] Re: Extra mouse cursor fixed on screen

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

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


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

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

** Summary changed:

- Extra mouse cursor fixed on screen
+ [nvidia] Extra mouse cursor fixed on screen

** Tags added: nvidia

** This bug has been marked a duplicate of bug 1827428
   Mouse cursor left frozen copy of itself

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

Title:
  [nvidia] Extra mouse cursor fixed on screen

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839008] [NEW] Extra mouse cursor fixed on screen

You have been subscribed to a public bug:

Inevitably the mouse cursor will become fixated on screen at the
position it was when the screen was unlocked. When I switch TTY and come
back the lock screen will change and I'll be able to move the fixed
mouse cursor to a new location. Only fix is to restart the computer and
the bug is guaranteed to recur. I am able to move the active cursor
around the screen but there is a persistent one that I am unable to
interact with.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  5 12:30:38 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
 nvidia, 418.56, 5.0.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:2229]
InstallationDate: Installed on 2019-08-02 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20DQ001LUS
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=51d296e6-a200-427d-8e49-36f04f92967a ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N19ET57W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20DQ001LUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN19ET57W(1.30):bd05/31/2018:svnLENOVO:pn20DQ001LUS:pvrThinkPadS5Yoga15:rvnLENOVO:rn20DQ001LUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad S5 Yoga 15
dmi.product.name: 20DQ001LUS
dmi.product.sku: LENOVO_MT_20DQ_BU_Think_FM_ThinkPad S5 Yoga 15
dmi.product.version: ThinkPad S5 Yoga 15
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sun Aug  4 18:49:18 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.4-1ubuntu3

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


** Tags: amd64 apport-bug disco third-party-packages ubuntu
-- 
Extra mouse cursor fixed on screen
https://bugs.launchpad.net/bugs/1839008
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to mutter in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1767536] Re: Accessing the WIFI section of the "Settings" window causes massive freezes

2019-08-05 Thread Brian

To copy a workaround from the thread linked above: `nm-connection-
editor` still works great.

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

Title:
  Accessing the WIFI section of the "Settings" window causes massive
  freezes

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

Also, I will attach journalctl -xb log taken as soon as I booted the
system and logged on this morning. It seems to me that as soon as
systemd started the gnome terminal server unit, related error messages
began to be generated.

Chrome/chromium had not been started at the time - it was autostarted by
your apport command quite a while later.

** Attachment added: "cold boot journalctl"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281063/+files/schizo-2001908-06-xb

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1838919/+attachment/5281060/+files/ProcCpuinfoMinimal.txt

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

apport information

** Tags added: apport-collected

** Description changed:

  This was a fresh amd64 installation with 18.10 desktop, upgraded to
  19.04 as soon as available. It has been getting worse over the last few
  weeks and is now so bad I can hardly type an email (or this bug report!)
  without having to fix many typos.
  
  journalctl shows many different gnome errors, so it is difficult to
  figure out which is the underlying cause and which are simply collateral
  damage.
  
  There are two sequences that appear first after a reboot, and the first
  of these has been reported many times on ubuntu releases going back for
  years:-
  
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module 
"canberra-gtk-module"
  
    and 
  
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.89/org/ayatana/NotificationItem/software_update_available
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-
  
  Is this a recent regression? I know for sure the system wasn't this
  unresponsive 3 weeks ago, but I cannot be sure when it started to go
  wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
  fiddled around with distance and battery state until I was sure the
  problem was somewhere else and started to check the system log.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu4.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 11:53:37 2019
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu4.19.04.1
   gnome-software-plugin-snap3.30.6-2ubuntu4.19.04.1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to disco on 2019-04-28 (98 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.04
+ Package: mutter
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
+ RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
+ Tags:  disco
+ Uname: Linux 5.0.0-23-generic x86_64
+ UpgradeStatus: Upgraded to disco on 2019-04-28 (99 days ago)
+ UserGroups: adm audio cdrom dip disk floppy lp lpadmin plugdev sambashare 
scans sudo video wireshark
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bu

[Bug 1838919] GsettingsChanges.txt

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1838919/+attachment/5281059/+files/GsettingsChanges.txt

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

Thanks for explaining Daniel #5. You will see I ran the command again.

However... It is interesting to see that even the apport-collect command
from a new terminal session triggered the canberra error.

brian@schizo:~$ apport-collect 1838919

(apport-gtk:21631): Gtk-WARNING **: 08:30:48.771: GTK+ module
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so cannot be loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not
supported.
Gtk-Message: 08:30:48.771: Not loading module "atk-bridge": The functionality
is provided by GTK natively. Please try to not load it.

(apport-gtk:21631): Gtk-WARNING **: 08:30:49.106: GTK+ module
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be
loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not
supported.
Gtk-Message: 08:30:49.106: Failed to load module "canberra-gtk-module"
The authorization page:

(https://launchpad.net/+authorize-token?oauth_token=t0cRSdJcr5xGQ4MLSbPG&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
brian@schizo:~$

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

Title:
Slow and lost keyboard and mouse events

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

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] ShellJournal.txt

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1838919/+attachment/5281062/+files/ShellJournal.txt

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1838919/+attachment/5281061/+files/ProcEnviron.txt

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839016] Re: Suspend is iterrupted by ALT key

2019-08-05 Thread Che Cheng

** Also affects: gnome-shell
   Importance: Undecided
   Status: New

** Project changed: gnome-shell => oem-priority

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

** Changed in: oem-priority
   Importance: Medium => High

** Changed in: oem-priority
 Assignee: (unassigned) => Che Cheng (cktenn)

** Description changed:

  When trying to suspend the system via pressing the power button in the
  system tray with ALT key pressed, it is possible to interrupt the system
  to enter sleep mode and fall back to screen lock. While trying to unlock
  the screen, the system goes to sleep immediately.
  
  Gnome-shell is able to suspend the system by drop-down menu in the
  system tray. By pressing ALT key or long-press the power button until it
  switches to suspend icon. The system will suspend if it is by the long-
  press power button, while with ALT key pressed, there is a failure rate
  that causes the suspend process to be interrupted.
  
  The second issue is that if the suspend process is interrupted, the
  locked screen is shown. While trying to unlock the screen by inputting
  password, the system will go sleeping after that.
  
  STEPS TO REPRODUCE:
  1. To suspend system via pressing the power button in the drop-down system 
tray with ALT key pressed.
  2. During system is going to sleep, e.g., screen going dark, emulate a key 
bounce by pressing ALT key again.
  
  RESULTS:
- The system going to sleep without a problem.
+ The locked screen shows up and goes to sleep after tens of seconds. While 
trying to unlock screen, system enter suspend after unlocking successfully.
  
  EXPECTED RESULTS:
- The locked screen shows up and goes to sleep after tens of seconds. While 
trying to unlock screen, system enter suspend after unlocking successfully.
+ The system going to sleep without a problem.
  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1

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

Title:
  Suspend is iterrupted by ALT key

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839016] [NEW] Suspend is iterrupted by ALT key

2019-08-05 Thread Che Cheng

Public bug reported:

When trying to suspend the system via pressing the power button in the
system tray with ALT key pressed, it is possible to interrupt the system
to enter sleep mode and fall back to screen lock. While trying to unlock
the screen, the system goes to sleep immediately.

Gnome-shell is able to suspend the system by drop-down menu in the
system tray. By pressing ALT key or long-press the power button until it
switches to suspend icon. The system will suspend if it is by the long-
press power button, while with ALT key pressed, there is a failure rate
that causes the suspend process to be interrupted.

The second issue is that if the suspend process is interrupted, the
locked screen is shown. While trying to unlock the screen by inputting
password, the system will go sleeping after that.

STEPS TO REPRODUCE:
1. To suspend system via pressing the power button in the drop-down system tray 
with ALT key pressed.
2. During system is going to sleep, e.g., screen going dark, emulate a key 
bounce by pressing ALT key again.

RESULTS:
The system going to sleep without a problem.

EXPECTED RESULTS:
The locked screen shows up and goes to sleep after tens of seconds. While 
trying to unlock screen, system enter suspend after unlocking successfully.


ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.1

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


** Tags: originate-from-1838504

** Also affects: gnome-shell
   Importance: Undecided
   Status: New

** No longer affects: gnome-shell

** Tags added: originate-from-1838504

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

Title:
  Suspend is iterrupted by ALT key

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838890] Re: Suspected memory leak in xenial backport of fix for CVE-2019-13012

This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu4.4

---
glib2.0 (2.48.2-0ubuntu4.4) xenial-security; urgency=medium

  * SECURITY REGRESSION: regression in last security update (LP: #1838890)
- debian/patches/CVE-2019-13012-regression.patch: fix a
  memory leak introduced by the last security update while
  not properly handled the g_file_get_patch function in
  gio/gkeyfilesettingsbackend.c.

 -- leo.barb...@canonical.com (Leonidas S. Barbosa)  Mon, 05 Aug 2019
12:09:36 -0300

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-13012

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

Title:
  Suspected memory leak in xenial backport of fix for CVE-2019-13012

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1838890/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1528319] Re: Scaling factors for HiDPI on multiple monitors

2019-08-05 Thread Chris Graham

I'm on an iMac, so I want to make use of my Retina (hj-dpi) screen,
while also using external screens that are not hi-dpi.

I can confirm no good X11 support for separate dpis per screen. I was
able to mess around with xrandr, but I got ghosting on my mouse cursor
that I could not resolve. Possibly I could have hand-configured an X
config for my particular screens, but seems like a lot of work and I
don't want to hard-code my screens.

The iMac screen doesn't work with all the resolutions selectable. In fact, my 
realistic  choices were basically either:
1) Full resolution with 200% scaling, and no usable second screen
2) 1/2 resolution with 100% scaling and usable second screen

I settled for '2'.

However, I read this issue and did see Wayland supported it. So I:
1) Logged in with Wayland
2) Ran gsettings set org.gnome.mutter experimental-features 
"['scale-monitor-framebuffer']"
3) Logged out (necessary)
4) Changed my dpis per screen in Display settings

It works reasonably well. Gnome apps are crisp on my Retina screens,
other apps are blurry due to presumable up-scaling of low-dpi rendering
to go onto the larger canvas.

Unfortunately of course Ubuntu has made Wayland non-default. I hope it
can become default again and all the issues with it (network protocol,
native app support) can be resolved, as I do think X11 is dated at this
point.

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

Title:
  Scaling factors for HiDPI on multiple monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1528319/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839012] [NEW] Asus A407Ma

2019-08-05 Thread Aliefan

Public bug reported:

Fingerprint gui on Asus A407Ma Zorin OS 15 not detect driver, please
solved it

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

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

Title:
  Asus A407Ma

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839010] [NEW] Touchpad does not work after installing Ubuntu

2019-08-05 Thread Adrian Barbuio

Public bug reported:

I previously had Windows 10 on my protab laptop. After wiping the hard
drive and installing Ubuntu 19.04 on the device, the touchpad ceases to
respond at all. I am using an external mouse currently.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  6 02:39:36 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-02-22 (164 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  Touchpad does not work after installing Ubuntu

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1793007] Re: gnome-disk-image-mounter creates loopback device but it is not mounted automatically

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

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

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

Title:
  gnome-disk-image-mounter creates loopback device but it is not mounted
  automatically

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838890] Re: Suspected memory leak in xenial backport of fix for CVE-2019-13012

2019-08-05 Thread Leonidas S. Barbosa

** Changed in: glib2.0 (Ubuntu)
   Status: New => In Progress

** Also affects: glib2.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu Precise)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Precise)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

** Changed in: glib2.0 (Ubuntu Trusty)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

** Changed in: glib2.0 (Ubuntu Xenial)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  Suspected memory leak in xenial backport of fix for CVE-2019-13012

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1838890/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839006] [NEW] No sound is playing from this laptop

2019-08-05 Thread Adrian Barbuio

Public bug reported:

I recently installed Ubuntu 19.04 on this protab laptop. In the settings
menu the sound output shows a headphone and a multichannel output
option. There is no sound coming out of either system, despite there
being sound detection demonstrated in the sound bars in the output menu
moving with the playback audio. I have tried force
restarting/reinstalling Alsa mixer and pulse audio and all the obvious
things such as checking sound level settings.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  6 02:09:12 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-02-22 (164 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  No sound is playing from this laptop

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838890] Re: Suspected memory leak in xenial backport of fix for CVE-2019-13012

2019-08-05 Thread Leonidas S. Barbosa

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  Suspected memory leak in xenial backport of fix for CVE-2019-13012

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1838890/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838902] Re: GNOME Control Center sticks when I add other keyboard in settings

2019-08-05 Thread Artyom Pozharov

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #632
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/632

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/632
   Importance: Unknown
   Status: Unknown

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

Title:
  GNOME Control Center sticks when I add other keyboard in settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1838902/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1048003] Re: clicking scrollbars above or below scrollbar button scrolls more than one screenful up or down

2019-08-05 Thread Paul White

Upstream bug was closed "RESOLVED NOTABUG" on 2012-10-09

Changes were made to Gtk and not evince. Old behaviour
of scrolling with left mouse button has been moved to
right mouse button. Change also applied to nautilus.

Checked still the case with evince 3.28.4 in Ubuntu 18.04.

Due to change in functionality I'm closing this as "Invalid"

** Changed in: evince (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  clicking scrollbars above or below scrollbar button scrolls more than
  one screenful up or down

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1825544] Re: Switch User menu item gone after upgrade to Ubuntu 19.04

2019-08-05 Thread Craig McQueen

For me, this bug just started happening when I did a software update
yesterday.

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

Title:
  Switch User menu item gone after upgrade to Ubuntu 19.04

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838948] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.

2019-08-05 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619:
  _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

Because this bug was reported against the wrong project (comment #1) it
has the wrong attachments. To correct that please run:

  apport-collect 1838919

Thanks for using 'ubuntu-bug' already. That's just a standard response
which was not entirely appropriate in this case.

I know, Chrome/Chromium's involvement sounds weird, but:

  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-

is from the Chromium source code and not from any part of Gnome Shell.

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1791574] Re: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage

This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1

---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from disco to eoan.

mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-2) experimental; urgency=medium

  * d/p/window-x11-Focus-a-window-in-the-active-workspace-as-take.patch:
- Fix possible crash on closing Java dialogs (Related to LP: #1834583)
d/p/metatest-Dispatch-the-destruction-instead-of-sleeping-aft.patch:
- Tests: don't wait too much after window destruction, causing failures

mutter (3.32.2+git20190711-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-1) experimental; urgency=medium

  * New upstream snapshot up to commit ccab0f470
- Fix No-input WM_TAKE_FOCUS dialogs causing GNOME Shell to hang
  and ensure we always have a window focused if we have a valid
  focus canididate (LP: #1834583)
- Don't crash on shell close / reload under X11 when releasing
  surface actor display resources (LP: #1826918)
  * d/p/debian/Revert-meson-Bump-meson-requirement-to-0.50.0.patch:
- Revert dependency on meson 0.50.0

mutter (3.32.2+git20190626-1ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from eoan to disco for SRU.

mutter (3.32.2+git20190626-1ubuntu1) eoan; urgency=medium

  * Merge with debian (LP: #1834493). Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190626-1) experimental; urgency=medium

  * New upstream snapshot release:
- Don't crash when try to focus unfocusable windows (LP: #1791574)
- Valgrind use-after-free warning fixes in the native backend
- renderer/native: add missing eglTerminate in EGLDevice error path
- Fix Alt+F2 -> restart to work again in X11
- window: Emit an error and return when trying to activate an unmanaged
  (LP: #1827401)
- Setting cursor to "none" doesn't hide it under Wayland
- Fix broken selected text in entries
- Tests memory fixes

mutter (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2-1) experimental; urgency=medium

  * New upstream release
  * d/p/clutter-evdev-disable-mousekeys-with-Numlock-ON.patch,
d/p/clutter-x11-disable-mousekeys-with-Numlock-ON.patch,
d/p/compositor-Destroy-window-actors-list-on-destruction.patch,
d/p/compositor-Disconnect-from-stage-signals-on-destruction.patch,
d/p/input-settings-Use-0-initialized-struct-for-kbd-a11y.patch:
- Dropped, merged upstream.
  * d/p/meson-add-back-default_driver-option.patch:
- Refreshed

 -- Iain Lane   Sun, 21 Jul 2019 20:51:33 +0100

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

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

Title:
  gnome-shell crashed with SIGABRT: assertion failed
  "window->display->focus_window != window" in meta_window_unmanage

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1826918] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_unref()

This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1

---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from disco to eoan.

mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-2) experimental; urgency=medium

  * d/p/window-x11-Focus-a-window-in-the-active-workspace-as-take.patch:
- Fix possible crash on closing Java dialogs (Related to LP: #1834583)
d/p/metatest-Dispatch-the-destruction-instead-of-sleeping-aft.patch:
- Tests: don't wait too much after window destruction, causing failures

mutter (3.32.2+git20190711-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-1) experimental; urgency=medium

  * New upstream snapshot up to commit ccab0f470
- Fix No-input WM_TAKE_FOCUS dialogs causing GNOME Shell to hang
  and ensure we always have a window focused if we have a valid
  focus canididate (LP: #1834583)
- Don't crash on shell close / reload under X11 when releasing
  surface actor display resources (LP: #1826918)
  * d/p/debian/Revert-meson-Bump-meson-requirement-to-0.50.0.patch:
- Revert dependency on meson 0.50.0

mutter (3.32.2+git20190626-1ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from eoan to disco for SRU.

mutter (3.32.2+git20190626-1ubuntu1) eoan; urgency=medium

  * Merge with debian (LP: #1834493). Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190626-1) experimental; urgency=medium

  * New upstream snapshot release:
- Don't crash when try to focus unfocusable windows (LP: #1791574)
- Valgrind use-after-free warning fixes in the native backend
- renderer/native: add missing eglTerminate in EGLDevice error path
- Fix Alt+F2 -> restart to work again in X11
- window: Emit an error and return when trying to activate an unmanaged
  (LP: #1827401)
- Setting cursor to "none" doesn't hide it under Wayland
- Fix broken selected text in entries
- Tests memory fixes

mutter (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2-1) experimental; urgency=medium

  * New upstream release
  * d/p/clutter-evdev-disable-mousekeys-with-Numlock-ON.patch,
d/p/clutter-x11-disable-mousekeys-with-Numlock-ON.patch,
d/p/compositor-Destroy-window-actors-list-on-destruction.patch,
d/p/compositor-Disconnect-from-stage-signals-on-destruction.patch,
d/p/input-settings-Use-0-initialized-struct-for-kbd-a11y.patch:
- Dropped, merged upstream.
  * d/p/meson-add-back-default_driver-option.patch:
- Refreshed

 -- Iain Lane   Sun, 21 Jul 2019 20:51:33 +0100

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

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

Title:
  gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay()
  from detach_pixmap() from meta_surface_actor_x11_dispose() from
  g_object_unref() from g_object_unref()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834493] Re: Update mutter to 3.32.2+git20190711

This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1

---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from disco to eoan.

mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-2) experimental; urgency=medium

  * d/p/window-x11-Focus-a-window-in-the-active-workspace-as-take.patch:
- Fix possible crash on closing Java dialogs (Related to LP: #1834583)
d/p/metatest-Dispatch-the-destruction-instead-of-sleeping-aft.patch:
- Tests: don't wait too much after window destruction, causing failures

mutter (3.32.2+git20190711-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-1) experimental; urgency=medium

  * New upstream snapshot up to commit ccab0f470
- Fix No-input WM_TAKE_FOCUS dialogs causing GNOME Shell to hang
  and ensure we always have a window focused if we have a valid
  focus canididate (LP: #1834583)
- Don't crash on shell close / reload under X11 when releasing
  surface actor display resources (LP: #1826918)
  * d/p/debian/Revert-meson-Bump-meson-requirement-to-0.50.0.patch:
- Revert dependency on meson 0.50.0

mutter (3.32.2+git20190626-1ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from eoan to disco for SRU.

mutter (3.32.2+git20190626-1ubuntu1) eoan; urgency=medium

  * Merge with debian (LP: #1834493). Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190626-1) experimental; urgency=medium

  * New upstream snapshot release:
- Don't crash when try to focus unfocusable windows (LP: #1791574)
- Valgrind use-after-free warning fixes in the native backend
- renderer/native: add missing eglTerminate in EGLDevice error path
- Fix Alt+F2 -> restart to work again in X11
- window: Emit an error and return when trying to activate an unmanaged
  (LP: #1827401)
- Setting cursor to "none" doesn't hide it under Wayland
- Fix broken selected text in entries
- Tests memory fixes

mutter (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2-1) experimental; urgency=medium

  * New upstream release
  * d/p/clutter-evdev-disable-mousekeys-with-Numlock-ON.patch,
d/p/clutter-x11-disable-mousekeys-with-Numlock-ON.patch,
d/p/compositor-Destroy-window-actors-list-on-destruction.patch,
d/p/compositor-Disconnect-from-stage-signals-on-destruction.patch,
d/p/input-settings-Use-0-initialized-struct-for-kbd-a11y.patch:
- Dropped, merged upstream.
  * d/p/meson-add-back-default_driver-option.patch:
- Refreshed

 -- Iain Lane   Sun, 21 Jul 2019 20:51:33 +0100

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

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

Title:
  Update mutter to 3.32.2+git20190711

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1827401] Re: gnome-shell crashed in meta_workspace_index -> meta_workspace_activate_with_focus -> meta_window_activate_full

This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1

---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from disco to eoan.

mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-2) experimental; urgency=medium

  * d/p/window-x11-Focus-a-window-in-the-active-workspace-as-take.patch:
- Fix possible crash on closing Java dialogs (Related to LP: #1834583)
d/p/metatest-Dispatch-the-destruction-instead-of-sleeping-aft.patch:
- Tests: don't wait too much after window destruction, causing failures

mutter (3.32.2+git20190711-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-1) experimental; urgency=medium

  * New upstream snapshot up to commit ccab0f470
- Fix No-input WM_TAKE_FOCUS dialogs causing GNOME Shell to hang
  and ensure we always have a window focused if we have a valid
  focus canididate (LP: #1834583)
- Don't crash on shell close / reload under X11 when releasing
  surface actor display resources (LP: #1826918)
  * d/p/debian/Revert-meson-Bump-meson-requirement-to-0.50.0.patch:
- Revert dependency on meson 0.50.0

mutter (3.32.2+git20190626-1ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from eoan to disco for SRU.

mutter (3.32.2+git20190626-1ubuntu1) eoan; urgency=medium

  * Merge with debian (LP: #1834493). Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190626-1) experimental; urgency=medium

  * New upstream snapshot release:
- Don't crash when try to focus unfocusable windows (LP: #1791574)
- Valgrind use-after-free warning fixes in the native backend
- renderer/native: add missing eglTerminate in EGLDevice error path
- Fix Alt+F2 -> restart to work again in X11
- window: Emit an error and return when trying to activate an unmanaged
  (LP: #1827401)
- Setting cursor to "none" doesn't hide it under Wayland
- Fix broken selected text in entries
- Tests memory fixes

mutter (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2-1) experimental; urgency=medium

  * New upstream release
  * d/p/clutter-evdev-disable-mousekeys-with-Numlock-ON.patch,
d/p/clutter-x11-disable-mousekeys-with-Numlock-ON.patch,
d/p/compositor-Destroy-window-actors-list-on-destruction.patch,
d/p/compositor-Disconnect-from-stage-signals-on-destruction.patch,
d/p/input-settings-Use-0-initialized-struct-for-kbd-a11y.patch:
- Dropped, merged upstream.
  * d/p/meson-add-back-default_driver-option.patch:
- Refreshed

 -- Iain Lane   Sun, 21 Jul 2019 20:51:33 +0100

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

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

Title:
  gnome-shell crashed in meta_workspace_index ->
  meta_workspace_activate_with_focus -> meta_window_activate_full

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus()

This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1

---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from disco to eoan.

mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-2) experimental; urgency=medium

  * d/p/window-x11-Focus-a-window-in-the-active-workspace-as-take.patch:
- Fix possible crash on closing Java dialogs (Related to LP: #1834583)
d/p/metatest-Dispatch-the-destruction-instead-of-sleeping-aft.patch:
- Tests: don't wait too much after window destruction, causing failures

mutter (3.32.2+git20190711-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190711-1) experimental; urgency=medium

  * New upstream snapshot up to commit ccab0f470
- Fix No-input WM_TAKE_FOCUS dialogs causing GNOME Shell to hang
  and ensure we always have a window focused if we have a valid
  focus canididate (LP: #1834583)
- Don't crash on shell close / reload under X11 when releasing
  surface actor display resources (LP: #1826918)
  * d/p/debian/Revert-meson-Bump-meson-requirement-to-0.50.0.patch:
- Revert dependency on meson 0.50.0

mutter (3.32.2+git20190626-1ubuntu1~19.04.1) disco; urgency=medium

  * No-change backport from eoan to disco for SRU.

mutter (3.32.2+git20190626-1ubuntu1) eoan; urgency=medium

  * Merge with debian (LP: #1834493). Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2+git20190626-1) experimental; urgency=medium

  * New upstream snapshot release:
- Don't crash when try to focus unfocusable windows (LP: #1791574)
- Valgrind use-after-free warning fixes in the native backend
- renderer/native: add missing eglTerminate in EGLDevice error path
- Fix Alt+F2 -> restart to work again in X11
- window: Emit an error and return when trying to activate an unmanaged
  (LP: #1827401)
- Setting cursor to "none" doesn't hide it under Wayland
- Fix broken selected text in entries
- Tests memory fixes

mutter (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.32.2-1) experimental; urgency=medium

  * New upstream release
  * d/p/clutter-evdev-disable-mousekeys-with-Numlock-ON.patch,
d/p/clutter-x11-disable-mousekeys-with-Numlock-ON.patch,
d/p/compositor-Destroy-window-actors-list-on-destruction.patch,
d/p/compositor-Disconnect-from-stage-signals-on-destruction.patch,
d/p/input-settings-Use-0-initialized-struct-for-kbd-a11y.patch:
- Dropped, merged upstream.
  * d/p/meson-add-back-default_driver-option.patch:
- Refreshed

 -- Iain Lane   Sun, 21 Jul 2019 20:51:33 +0100

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

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

Title:
  [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung
  in (varying functions under) meta_stack_get_default_focus_window()
  from meta_window_x11_focus()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

Daniel post #2. That was exactly how I opened this bug report, so what
exactly are you missing?

Daniel post #3. I don't use Chromium, by preferred browser is stock
vanilla Chrome from their own repository. I did not think Chrome was
delivered as a snap - are you sure your comment is relevant?

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1791574] Update Released

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

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

Title:
  gnome-shell crashed with SIGABRT: assertion failed
  "window->display->focus_window != window" in meta_window_unmanage

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1826918] Update Released

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

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

Title:
  gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay()
  from detach_pixmap() from meta_surface_actor_x11_dispose() from
  g_object_unref() from g_object_unref()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834493] Update Released

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

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

Title:
  Update mutter to 3.32.2+git20190711

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1827401] Update Released

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

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

Title:
  gnome-shell crashed in meta_workspace_index ->
  meta_workspace_activate_with_focus -> meta_window_activate_full

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834583] Update Released

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

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

Title:
  [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung
  in (varying functions under) meta_stack_get_default_focus_window()
  from meta_window_x11_focus()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

The GL errors appear to be from Chrome/Chromium. Not Gnome Shell at all.
Although it does sound like they're related to snaps too:

https://wiki.ubuntu.com/DesktopTeam/GNOMESnapStartup

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

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

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1838919] Re: Slow and lost keyboard and mouse events

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1838919

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  Slow and lost keyboard and mouse events

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1748036] Re: .pam_environment not applied if home directory is encrypted