This started happening a few months ago, I would be minding my own Ubuntu business and then suddenly I can’t left click.
After much digging and stupid AI querying, I added something to disabled power management to my boot sequence. That seems to minimize the problems but I still get the problem every 5 minutes or so.
To temporarily fix the problem I Ctrl-alt F3 then F2 to come back to. GNOME.
I tried with a mint usb and I got the same problem. I thought it was then maybe a mouse problem but the pointer does the same no matter what mouse I use and every mouse I tested worked fine on another Ubuntu of the same release. So I think maybe it is some sort of hardware and driver combination and to power management.
I see lots of posts of past years but nothing more recently, but no real solutions or explanations for what might be happening.
Okay looks like a start up script will be the thing to do next.


I did this. It does work but when I restart I get the darn problem again.
Google “<your bootloader> add kernel parameter”. Likely Grub in your case.
Although this boot parameter is merely a workaround. I’ve had some issues with the flat metallic Kinston thumbdrives getting filesystem corruption because they overheat and quickly dis/reconnect even with working powersaving. Not that this must happen to you, but all i’m saying is that you still better find the root cause or get another mouse.
In order to make the kernel option persist, you will have to add the option to your bootloader config. Ubuntu probably uses grub, but in any case, I never can remember how to configure any of the bootloaders. Someone here can probably help out (or it’ll be a quick search away, I’m sure).
Not the same distro, but on my system, the relevant file is located at
/etc/default/grub. Find the line that saysGRUB_CMDLINE_LINUX, uncomment it if necessary, and add your kernel parameter to it (mine hasGRUB_CMDLINE_LINUX="acpi_enforce_resources=lax", for historical reasons). Then rungrub-mkconfigwith appropriate arguments to regenerate your grub configuration.How about a command that runs at every startup then? Some call it autostart and it could be any script you make. Not the solution but an effective workaround.