Re: [Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
Daniel
I am Brian's wife, Jane
I am devastated to let you know that Brian succumbed to his prostate
cancer and died a few weeks ago
Please let everyone know
Thanks
Jane Burch
On 7/8/20 7:50 pm, Daniel van Vugt wrote:
> Thank you for reporting this bug to Ubuntu.
> Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
>
> See this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> We appreciate that this bug may be old and you might not be interested
> in discussing it any more. But if you are then please upgrade to the
> latest Ubuntu version and re-test. If you then find the bug is still
> present in the newer Ubuntu version, please add a comment here telling
> us which new version it is in and change the bug status to Confirmed.
>
> ** Changed in: gnome-shell (Ubuntu)
> Status: Incomplete => Won't Fix
>
> ** Changed in: mutter (Ubuntu)
> Status: Incomplete => Won't Fix
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Won't Fix
Status in mutter package in Ubuntu:
Won't Fix
Bug 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
[Desktop-packages] [Bug 1838919] ShellJournal.txt
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331424/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-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
[Desktop-packages] [Bug 1838919] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331422/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-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
[Desktop-packages] [Bug 1838919] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331423/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-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
Re: [Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
On 24/2/20 3:12 pm, Daniel van Vugt wrote:
> Actually I should have just continued from comment #27. To do that
> please run:
>
>mv ~/.local/share/gnome-shell/extensions ~/old-extensions
Oops! I had already run the "dconf reset"!
Never mind, I was not aware of having changed the settings from their
original defaults. I presume they were residual from an earlier release.
> and then reboot. Any improvement?
The keyboard hang happens fairly frequently, but perhaps less often than
before the reset. Also, mouse hangs are rare and recover automatically,
so I can't be certain there is still a problem.
I will run the apport-collect, but I am content to live with the problem
and re-assess when 20.04 is available.
Thanks for caring!
Brian
> ** Changed in: gnome-shell (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: mutter (Ubuntu)
> Status: New => Incomplete
>
** 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:
[Desktop-packages] [Bug 1838919] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331420/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-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
[Desktop-packages] [Bug 1838919] GsettingsChanges.txt
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5331421/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-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:
[Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
Sorry for the delay. The problem still exists under 19.10 desktop, but
does not occur quite as often. However, it is slightly harder to escape
from... I either need to wait 20+ seconds uselessly pressing keys I will
have to subsequently delete, or tab to another command prompt, type
something in easily, then return to the "stuck" prompt.
My comment is only to bring the bug report up to date and keep it open.
We are only a few weeks from the 20.04 release, where this bug will be
much more important if still present.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Won't Fix
Status in mutter package in Ubuntu:
Won't Fix
Bug 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
[Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
I upgraded both my Ubuntu Desktop and UbuntuStudio systems to 19.10 Eoan
(with gnome mostly at 3.34). The symptoms have not changed... my desktop
still hangs, loses keyboard events, and the log fills with the GTK 2/3
conflict messages. Meanwhile my Studio system behaves perfectly!
The log messages are generated by nautilis, gnome terminal, thunderbird,
and several other applications, but I do not think they are the culprits
- just the victims of something unseen.
The Studio system also has many GTK2 packages installed alongside the
GTK3 ones, so there isn't a simple explanation for the difference in
behaviour. I will do a side-by-side comparison of installed packages to
see if there is some sort of clue.
Meanwhile, I would be grateful if anyone could suggest how to identify
the guilty component. I would love to purge it!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug 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:
[Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
I didn't see any problems logging on with gnome on xorg, or starting the
first terminal session.
However, as soon as I started the second terminal, the GTK2/GTK3 error
messages poured out. Opening a new tab on the same window does not
generate the messages.
This sounds like your gnome bug report - it doesn't look like a widget,
or an application, but something more fundamental.
I wonder why my system even has the i386 packages installed - were they
pulled in by an application (such as wine) which isn't installed on my
laptop? What is the best way to locate the culprit - I now know it isn't
Chrome, thunderbird, nautilus or netbeans. It's hard to believe gnome-
terminal is the root cause.
** 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
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug 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:
Re: [Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
On 14/8/19 8:22 pm, Traumflug wrote:
> Installed packages don't matter if their content isn't in use. It does
> matter whether you run an X11 or a Wayland session.
>
> To switch between both, log out to get to the login screen. There is a
> gears icon right above the password entry field, click on it. This
> should open a menu allowing to choose between "Ubuntu on Xorg" and
> "Ubuntu on Wayland". Having this choice done, log in, you'll be in the
> selected type of session.
I had forgotten the gear wheel.. the last time I used it was when unity
came out as the new default and I preferred Gnome Classic. Thanks for
reminding me.
> Basically, all applications work in both session types, but there are a
> number of smaller visual distinctions. For example, Firefox draws its
> menu inside the window bar on Wayland, while it draws the menu under the
> window bar on X11. Also, on X11 there's a process "Xorg" running, while
> on Wayland there's a process "XWayland" (or similar).
The default on the desktop system was "ubuntu", so I changed to "Gnome
on Xorg". The presentation details are different (obviously) but don't
bother me. However, I get exactly the same errors logged and slow input
events:-
Aug 15 07:21:43 schizo gnome-control-c[8320]: 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.
Aug 15 07:21:43 schizo gnome-control-c[8320]: Not loading module
"atk-bridge": The functionality is provided by GTK natively. Please try
to not load it.
Aug 15 07:21:44 schizo gnome-control-c[8320]: 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.
Aug 15 07:21:44 schizo gnome-control-c[8320]: Failed to load module
"canberra-gtk-module"
Aug 15 07:21:44 schizo gnome-control-c[8320]: 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.
Aug 15 07:21:44 schizo gnome-control-c[8320]: Failed to load module
"canberra-gtk-module"
I will try again but this time only start a terminal session. I realise
there is a lot of processes running to support a single graphical user
session, but I'll keep Chrome and Thunderbird out of the variables.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug 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:
[Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
Thank you very much for your suggestion #21, Traumflug. I read the issue
you quoted and to be honest, I was quite disappointed in the responses
so far.
The symptoms sound very similar to those I reported here. I compared the
wayland packages on my desktop (slow or lost mouse and keyboard events)
with those on my laptop (ubuntu studio), which works satisfactorily. I
will attach a file containing the two dpkg lists for comparison.
I really don't understand the wayland architecture, but was happy to use
the recommended workaround when running sudo gui programs such as
gparted.
I notice two differences and wonder whether either of them might account
for the diference between my two systems?
1. The desktop has three i386 old packages not installed on the laptop.
Perhaps I should delete them?
2. The desktop has the xwayland package installed, but the laptop does
not.
What do you think? Is this helpful in tracking down the root cause of
the problem? Is there anything I can do to assist with further
diagnosis, given I have two systems side-by-side for comparison?
** 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
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug 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
[Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
I had a bit of a brainwave this morning - or perhaps just awoke from my
stupidity!
I also have a laptop which runs ubuntu studio 19.04 amd64. At the
moment, my desktop which is suffering has the 5.0.0-23-generic kernel.
The laptop has the 5.0.0-21-lowlatency kernel, BUT does not have all
these problems.
The laptop also has gtk2 and gtk3 packages installed, although I haven't
yet done a package-by-package diff.
As far as I can remember, they both have mostly the same applications,
although studio has a lot more. The laptop currently has upgrades
waiting to be installed for the kernel, chromium, chrome and mutter (and
quite a few more packages).
Should I upgrade those packages on the laptop one at a time, to see
whether the same problem appears?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug 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
[Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug 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-snap3.30.6-2ubuntu4.19.04.1
SourcePackage: gnome-software
UpgradeStatus: Upgraded to disco on 2019-04-28 (98 days ago)
---
ProblemType: Bug
ApportVersion:
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug 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-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
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug 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.
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug 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
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-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:
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-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
[Desktop-packages] [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_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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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
[Desktop-packages] [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"
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-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
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-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
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug 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-snap3.30.6-2ubuntu4.19.04.1
SourcePackage: gnome-software
UpgradeStatus: Upgraded to disco on 2019-04-28 (98 days ago)
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1838919] [NEW] Slow and lost keyboard and mouse events
Public bug reported: 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) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events Status in gnome-software package in Ubuntu: New Bug 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
[Desktop-packages] [Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04
upgraded from 17.04 to 17.10 64-bit desktop. ASUS Transformer T300 CHI- FL005H. kernel 4.13.0-32-generic and gnome-settings-daemon 3.26.2-0ubuntu0.1 syslog and journalctl spammed exactly as described - gdm3 and gsd- backlight-helper --set-brightness I can confirm "systemctl stop iio-sensor-proxy" causes these messages to stop, but less frequent errors from org.gnome.Shell.desktop are logged repeatedly, e.g. Error.checkin_request.cc(211) failed to get checking response. Fetcher failed. Retrying. Followed by various other org.gnome.Shell.desktop messages. I can provide a log if they might be useful, but I suspect they are triggered by killing the iio-sensor-proxy and so are probably not very relevant to the original bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1584457 Title: gsd-backlight-helper spamming the logs since upate to 16.04 Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Xenial: Confirmed Bug description: Since updating to 16.04 from 14.04, I have the syslog spammed by: SEC: May 22 13:26:43 samsung-romano pkexec[21248]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 1766] SEC: May 22 13:26:43 samsung-romano pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1153) SEC: May 22 13:26:43 samsung-romano pkexec: pam_systemd(polkit-1:session): Cannot create session: Already running in a session SEC: May 22 13:26:43 samsung-romano pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device SEC: May 22 13:26:43 samsung-romano pkexec[21249]: romano: Executing command [USER=root] [TTY=unknown] [CWD=/home/romano] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 4322] SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: Error executing command as another user: Not authorized SYS: May 22 13:26:43 samsung-romano gnome-session[1454]: This incident has been reported. every couple of seconds or so. There is no really need to change brightness... how can I stop it? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 563774] Re: Invalid EDID for Dell SP2309W in VGA mode
On 09/01/14 01:35, Christopher M. Penalver wrote: Brian Burch, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . The only machine I could test with normally runs headless, so it took a while to schedule some maintenance time - sorry for the delay. I booted the 14.04 iso from DVD (too big for a CD and the machine's BIOS would not boot from a USB stick). The Dell screen displayed the splash screen and normal desktop approx 1 inch shifted to the right, exactly as originally reported. I was disappointed, and was about to give up. Something made me think to perform the screen auto-adjust function... the image wiggled around for a moment, and then displayed PERFECTLY! That machine normally runs ubuntu 12.04 LTS, and has recently been updated with the latest fixes. I booted the production 12.04 system where the desktop was misaligned and deliberately set to a low resolution so the entire image would be visible. I changed the screen resolution settings to the optimal value and it was aligned perfectly because the screen had already adjusted and memorised this SVGA resolution alignment. I presume the quirk for my display was incorporated in a 12.04 repository update at some time in the past, but I had overlooked the notice and so continued using the sub-optimal resolution. Thank you for suggesting that I run this test. You can close the bug for 12.04, 14.04, and any other releases it might apply to. Regards, Brian If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p xserver-xorg-video-nouveau REPLACE-WITH-BUG-NUMBER Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided = Low ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed = Incomplete ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Assignee: Chris Halse Rogers (raof) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/563774 Title: Invalid EDID for Dell SP2309W in VGA mode Status in “xserver-xorg-video-nouveau” package in Ubuntu: Incomplete Bug description: Binary package hint: xorg This monitor has a preferred resolution of 2048x1152 @ 60Hz. The desktop does not fill the display and leaves a 2 cm black strip on the left margin. The monitor manual adjustments do not permit the image to be moved or expanded to fill the screen. Some of the lower resolutions fill the screen, so I am confident the monitor does not have a hardware fault. This problem is reported against karmic, with the screen attached through a kvm switch. I have reproduced the same symptoms under lucid beta - so I will attach the lucid diagnostics because xorg on that system is at the latest level. My karmic and lucid systems use the nVidia NOUVEAU driver, but the same symptoms also occur using the proprietary drivers at version 185 (from the ubuntu repository), and also with version 195 (from the nvidia ppa repository). ProblemType: Bug Architecture: i386 Date: Thu Apr 15 13:03:38 2010 DistroRelease: Ubuntu 9.10 Lsusb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: stem manufacturer System Product Name NonfreeKernelModules: nvidia Package: xserver-xorg 1:7.4+3ubuntu10 ProcCmdLine: root=/dev/mapper/lvmG0-root ro bootdegraded=true nohz=off quiet splash ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-20.58-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu10 libgl1-mesa-glx 7.6.0-1ubuntu4 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu2.1 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 SourcePackage: xorg Uname: Linux 2.6.31-20-generic i686 dmi.bios.date: 07/20/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1903 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2
