After a certain amount of time after the session is launched, mouse clicks are no longer accepted

Bug #1904671 reported by Hidetsugu TAKAHASHI
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

X11, Wayland, the Gnome Desktop does not recognize mouse clicks and drags after several tens of minutes after launching. However, it does recognize the movement of the mouse cursor.

[How To Reploduce]

1. login in a Gnome session.
2. launch some applications.
3. use it for a few dozen minutes.
4. attempt to click and drag with a mouse or other pointing device.

[Actual Result]

I can no longer select mouse click application windows, activity buttons, dashes, etc.

[Expect Result]

I will accept mouse clicks until the end of the session, and possibly hope that the event is executed when the click is made.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-release-upgrader-core 1:20.10.13
ProcVersionSignature: Ubuntu 5.8.0-28.30-lowlatency 5.8.14
Uname: Linux 5.8.0-28-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 18 13:29:28 2020
InstallationDate: Installed on 2018-05-20 (913 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ja_JP.UTF-8
 SHELL=/usr/bin/fish
RebootRequiredPkgs:
 gnome-shell
 linux-image-5.8.0-29-lowlatency
 linux-base
 linux-image-5.8.0-29-generic
 linux-base
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to groovy on 2020-10-25 (23 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed
VarLogDistupgradeApttermlog: Error: [Errno 13] 許可がありません: '/var/log/dist-upgrade/apt-term.log'
VarLogDistupgradeTermlog:

Revision history for this message
Hidetsugu TAKAHASHI (manzyun) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

You've filed this bug against ubuntu-release-upgrader, but don't seem to describe a problem related to the upgrade process, so I'm a little confused by that.

I get the (uneducated) feeling that it relates to GNOME, or the kernel (linux) but I'm unsure sorry. I would likely explore that probably using `xev` to ensure the mouse events are still recognized (ie. leaving that in a corner with terminal window visible)...

It may help if you clarify why you filed against the upgrade process.

Revision history for this message
Hidetsugu TAKAHASHI (manzyun) wrote :

Thank you response Mr.Chris.

> You've filed this bug against ubuntu-release-upgrader, but don't seem to describe a problem related to the upgrade process, so I'm a little confused by that.

I saw this after upgrading with the `apt full-upgrate` command, so I chose `ubuntu-release-upgrader` and reported a bug. I'm sorry, my mistake.

> I get the (uneducated) feeling that it relates to GNOME, or the kernel (linux) but I'm unsure sorry. I would likely explore that probably using `xev` to ensure the mouse events are still recognized (ie. leaving that in a corner with terminal window visible)...

I'm unfortunately, I didn't know how to output real-time event logs in GNOME or the kernel. I may be able to investigate the cause with `xev`. Thanks for the helpful information.

By the way, here's my feeling that I just noticed.

From #1 :
> [How To Reploduce]
>
> 1. login in a Gnome session.
> 2. launch some applications.
> 3. use it for a few dozen minutes.
> 4. attempt to click and drag with a mouse or other pointing device.

The contents of number 3 are
"Leave it for a few dozen minutes without doing anything."
may be correct.

Because I encountered this phenomenon when I took a few dozen separate seats without locking the screen and tried to operate it again.

I'm new to reporting bug and I'm sure there is some information missing from the information I provide.

I will continue to look into this phenomenon and get back to you as best I can.

Revision history for this message
Hidetsugu TAKAHASHI (manzyun) wrote :

I'm not sure if this information is useful or not.

I ran into the same phenomenon, so I ran the `xev` command to see if the input information was detected.

It was detected without problems, and at the same time, the selection of other windows themselves and their contents became possible after invoking the `xev` command.

You hope this helps.

affects: ubuntu-release-upgrader (Ubuntu) → xorg (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It sounds like gnome-shell is frozen/crashed and Xorg is still running.

Please:

1. Remove any gnome-shell extensions you may have installed and log out and in again.

2. If the problem still happens, check the Extensions app and disable all extensions. Then log out and in again.

3. If the problem still happens, please follow these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

affects: xorg (Ubuntu) → gnome-shell (Ubuntu)
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.