Linux

62949 readers

502 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Help with mouse not clicking (lemmy.today)

submitted 1 day ago* (last edited 9 hours ago) by altphoto@lemmy.today to c/linux@lemmy.ml

15 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] detonational_VuSE@lemmy.ml 2 points 18 hours ago (1 children)

Your problem is probably an ACPI setting, if that helps you look up an explanation. Try putting usbcore.autosuspend=-1 in the kernel options on your bootloader. If that works, that's definitely the problem, so then either you're good without it or if you still want autosuspend for everything else (good for battery life on a laptop) you should look into a more fine grain approach.

[–] altphoto@lemmy.today 2 points 17 hours ago (3 children)

I did this. It does work but when I restart I get the darn problem again.

[–] MonkderVierte@lemmy.zip 3 points 9 hours ago* (last edited 9 hours ago)

Google " 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.

[–] timroerstroem@feddit.dk 1 points 14 hours ago (1 children)

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).

[–] nyan@sh.itjust.works 2 points 8 hours ago

Not the same distro, but on my system, the relevant file is located at /etc/default/grub. Find the line that says GRUB_CMDLINE_LINUX, uncomment it if necessary, and add your kernel parameter to it (mine has GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax", for historical reasons). Then run grub-mkconfig with appropriate arguments to regenerate your grub configuration.

[–] anonklay@lemmy.world 1 points 15 hours ago

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.