Mouse left button not being noticed when clicked under Wayland - works under x11

[Mark Rogers]

Connected other mice, unplugging/rebooting/replugging in mouse has no affect.

However booting into X11 from the login screen fixes the mouse issue! If I try to login with Wayland then the problem reemerges.

Ive even enabled "Pre-Release Updates and downloaded all the updated files in the hope of fixing the issue - it didnt.

So HELP!

Even though I have a working system I would prefer to be working under Wayland.

Cheers in advance

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-release-upgrader-core 1:17.10.8
Uname: Linux 4.13.0-041300-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 14 15:57:30 2018
InstallationDate: Installed on 2017-09-06 (129 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170905)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeTermlog:

[Daniel van Vugt (vanvugt)]

Please let us know if bug 1181666 sounds like the same issue as you experience. If not then please elaborate by telling us what you're trying to click on that's not responding.

[Mark Rogers (thinkingbeyondthesquare)]

More info:

The issue is both at the login screen and within the wayland desktop. Left mouse clicks on any part of the interface are not recognised, even though I can move the mouse.

bug 1181666 sounds familiar however logouts/reboots do not reset the mouse. It is as if the default starting setting for the mouse have somehow disable left mouse clicks.

If from the login screen I select the X11 graphics subsystem then the mouse works as expected.

The other thing is that the mouse was working normally under wayland in 17.10 up until I reported the bug - so something changed, and Im guessing that change was in the low level mouse settings for wayland.

Hope that helps a little more.

BTW the files uploaded were generated under the X11 session, not the wayland session.

Please let me know what you need me to do to generate any other log/config file info you need.

Cheers

[Launchpad Janitor (janitor)]

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

[Mark Rogers (thinkingbeyondthesquare)]

Update:

I was running the: paulo-miguel-dias/mesa build
and the: oibaf/graphics-drivers build

I uninstalled both and reverted to the standard ubuntu drivers/setup. This fixed the mouse issue.
As both of the above adons have some popularity one of them may have been the cause of the issue - though cant confirm which one. Perhaps it was because I was running both that caused a configuration issue after an update - all just conjecture, however I now have a working Wayland session now.

Hope this sheds some light on what might have happened.

[Daniel van Vugt (vanvugt)]

Please don't reopen this bug. It is closed because of comment #5.

I have reopened bug 1747568 instead.

[Enigma (enigma0)]

Well... It doesn't sound like it's fixed & certainly not invalid.

If it still doesn't work when using updated versions of packages available in those PPA's, it's not really fixed.

Is there a way to mark it as duplicate instead?

[Enigma (enigma0)]

So.. I marked it as a duplicate of the bug you mentioned. Still.. invalid really doesn't seem appropriate.

The description says:

Invalid:
Not a bug. May be a support request or spam.

[Daniel van Vugt (vanvugt)]

Invalid in this context actually means "not a bug in Ubuntu, but maybe still a bug". It does not mean the issue does not exist, only that it's not a bug originating from the Ubuntu archive.

We have to use Invalid only because no better status exists in Launchpad.