| 2019-08-05 02:06:30 |
Brian Burch |
bug |
|
|
added bug |
| 2019-08-05 05:52:34 |
Olivier Tilloy |
affects |
gnome-software (Ubuntu) |
gnome-shell (Ubuntu) |
|
| 2019-08-05 07:35:23 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
New |
Incomplete |
|
| 2019-08-05 07:39:22 |
Daniel van Vugt |
bug task added |
|
mutter (Ubuntu) |
|
| 2019-08-05 07:39:33 |
Daniel van Vugt |
mutter (Ubuntu): status |
New |
Incomplete |
|
| 2019-08-05 22:32:39 |
Brian Burch |
tags |
amd64 apport-bug disco |
amd64 apport-bug apport-collected disco |
|
| 2019-08-05 22:32:41 |
Brian Burch |
description |
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-snap 3.30.6-2ubuntu4.19.04.1
SourcePackage: gnome-software
UpgradeStatus: Upgraded to disco on 2019-04-28 (98 days ago) |
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-snap 3.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 |
|
| 2019-08-05 22:32:43 |
Brian Burch |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5281058/+files/Dependencies.txt |
|
| 2019-08-05 22:32:45 |
Brian Burch |
attachment added |
|
GsettingsChanges.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5281059/+files/GsettingsChanges.txt |
|
| 2019-08-05 22:32:47 |
Brian Burch |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5281060/+files/ProcCpuinfoMinimal.txt |
|
| 2019-08-05 22:32:49 |
Brian Burch |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5281061/+files/ProcEnviron.txt |
|
| 2019-08-05 22:32:51 |
Brian Burch |
attachment added |
|
ShellJournal.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5281062/+files/ShellJournal.txt |
|
| 2019-08-05 22:42:22 |
Brian Burch |
attachment added |
|
cold boot journalctl https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281063/+files/schizo-2001908-06-xb |
|
| 2019-08-06 02:00:43 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
Incomplete |
New |
|
| 2019-08-06 02:00:46 |
Daniel van Vugt |
mutter (Ubuntu): status |
Incomplete |
New |
|
| 2019-08-06 03:59:39 |
Daniel van Vugt |
bug |
|
|
added subscriber Daniel van Vugt |
| 2019-08-06 05:12:53 |
Brian Burch |
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 |
|
| 2019-08-06 05:13:40 |
Brian Burch |
attachment added |
|
dpkg list https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281101/+files/schizo-2019-08-06-allpackages-txt |
|
| 2019-08-11 22:54:42 |
Traumflug |
bug watch added |
|
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510 |
|
| 2019-08-11 22:55:07 |
Traumflug |
bug |
|
|
added subscriber Traumflug |
| 2019-08-14 06:50:26 |
Brian Burch |
attachment added |
|
dpkg list comparison for wayland https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5282468/+files/2019-08-14-wayland-packages-compared |
|
| 2019-08-14 23:27:08 |
Brian Burch |
attachment added |
|
journalctl with xorg when starting a second terminal session https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5282548/+files/2019-08-15-xorg-gnome-second-terminal |
|
| 2020-01-24 09:10:35 |
Daniel van Vugt |
mutter (Ubuntu): status |
New |
Won't Fix |
|
| 2020-01-24 09:10:40 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
New |
Won't Fix |
|
| 2020-02-24 04:55:57 |
Daniel van Vugt |
tags |
amd64 apport-bug apport-collected disco |
amd64 apport-bug apport-collected eoan |
|
| 2020-02-24 04:56:02 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
Won't Fix |
New |
|
| 2020-02-24 04:56:05 |
Daniel van Vugt |
mutter (Ubuntu): status |
Won't Fix |
New |
|
| 2020-02-24 05:13:01 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
New |
Incomplete |
|
| 2020-02-24 05:13:04 |
Daniel van Vugt |
mutter (Ubuntu): status |
New |
Incomplete |
|
| 2020-02-27 00:40:38 |
Brian Burch |
description |
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-snap 3.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 |
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-snap 3.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
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 19.10
Package: mutter
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
Tags: eoan
Uname: Linux 5.3.0-26-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (131 days ago)
UserGroups: adm audio cdrom dip disk floppy lp lpadmin plugdev sambashare scans sudo video wireshark
_MarkForUpload: True |
|
| 2020-02-27 00:40:40 |
Brian Burch |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5331420/+files/Dependencies.txt |
|
| 2020-02-27 00:40:41 |
Brian Burch |
attachment added |
|
GsettingsChanges.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5331421/+files/GsettingsChanges.txt |
|
| 2020-02-27 00:40:43 |
Brian Burch |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5331422/+files/ProcCpuinfoMinimal.txt |
|
| 2020-02-27 00:40:44 |
Brian Burch |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5331423/+files/ProcEnviron.txt |
|
| 2020-02-27 00:40:46 |
Brian Burch |
attachment added |
|
ShellJournal.txt https://bugs.launchpad.net/bugs/1838919/+attachment/5331424/+files/ShellJournal.txt |
|
| 2020-08-07 09:50:29 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
Incomplete |
Won't Fix |
|
| 2020-08-07 09:50:32 |
Daniel van Vugt |
mutter (Ubuntu): status |
Incomplete |
Won't Fix |
|
