Strange mouse problem Ubuntu 20.04

[stripes theotoky]

Start Ubuntu and log in with the graphical interface and everything is fine. Fifteen minutes later no mouse clicks are recognised outside of Firefox and only some within it. I can read pages in open tabs, open new tabs and search. I cannot click to get a list of open tabs I cannot close of minimise Firefox. Trying to open other programs from the menu on the side highlights the program when the cursor is over it and it does not lose the highlight when the cursor moves away, clicking any of them achieves nothing.

I have tried reinstalling sudo apt reinstall xserver-xorg-input-all and restarting but with no effect.

Restarting the box fixes the mouse for another 15 minutes. I will restart it again now and not open firefox to see if the problem occurs with other programs.

All the best

Stripes

--

Stripes Theotoky

39°37'02.4"N 19°55'17.1"E

39.617334, 19.921417

 

[stripes theotoky]

Follow up. The mouse remains partly useable in whatever program is open at the time. Scroll wheel stops working for a few seconds and when it comes back it is not possible to click on anything outside the program that is running. I have tested with firefox, krita libreoffice and terminal. Some click functionality is lost in the programs (access to the menus for example) but overall they remain useable. No other program can be clicked on.

I have tried Alt Ctrl F7, Alt Ctrl F1 but this doesn't restore the mouse. from a terminal have tried sudo modprobe -r psmouse, sudo modprobe psmouse proto=imps, reinstalled ubuntu-desktop. None of it has made any difference at all.

Any suggestions?

Regards

Stripes

[Duncan Roe]

Hi Stripes,

On Fri, May 14, 2021 at 10:02:11PM +0100, mlug wrote:
> Follow up. The mouse remains partly useable in whatever program is open at
> the time. Scroll wheel stops working for a few seconds and when it comes
> back it is not possible to click on anything outside the program that is
> running. I have tested with firefox, krita libreoffice and terminal. Some
> click functionality is lost in the programs (access to the menus for
> example) but overall they remain useable. No other program can be clicked
> on.
>
> I have tried Alt Ctrl F7, Alt Ctrl F1 but this doesn't restore the mouse.
> from a terminal have tried sudo modprobe -r psmouse, sudo modprobe psmouse
> proto=imps, reinstalled ubuntu-desktop. None of it has made any difference
> at all.
>
> Any suggestions?

Suggest you check logs: Xorg.0.log in particular.

Something else to try: Since Ctl-Alt-F1 works, try killing the X server in lieu
of rebooting (pkill X). After you get back in, is the mouse working again?
If not, maybe something has gone wrong in the kernel: check system logs for an
OOPS, BUG or anything else that looks unusual.

Cheers ... Duncan.

[stripes theotoky]

I have checked the logs and can find nothing that looks out of line.

I have looked in Xorg.0.log grepping for Mouse, Logitech and M325 show nothing out of line that I can see.

dmesg and kern.log show nothing apparently out of line.

Looking in /var/log/syslog I get the following message approximately 14,000 times a second. This appears to be the only message in that file. This message first seems to have first appeared in /var/log/syslog.1 yesterday at about 07:47.

Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a clutter actor or GTK widget with ::destroy signal detected or using the destroy(), dispose() or remove() vfuncts. Because it would crash the application, it has been blocked. The offending callback was SourceFunc()

I wonder if there is nothing wrong with the mouse and the box is being flooded with error messages.

Any ideas on how to find and kill this error or show that it is not relevant to the mouse issue?

Regards

Stripes

[stripes theotoky]

More information /var/log/syslog grew to 155GB and ate all of the disk space almost the entire file was filled with the GTK error

Gnome-shell [2488]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a clutter actor or GTK widget with ::destroy signal detected or using the destroy(), dispose() or remove() vfuncts. Because it would crash the application, it has been blocked. The offending callback was SourceFunc()

Moved syslog onto a back up drive, the computer starts and runs but still lose mouse clicks after about 5 min and syslog has been recreated and grown to 30GB already also with the same error.

Regards

Stripes

[stripes theotoky]

Half of what I wrote seems to not be connected to the mouse issue at all. I have fixed the log file problem by purging all snap packages off this system and replacing with debs. The only issue outstanding is the mouse so where I am up to.

Log in as normal and everything works for about 5 min. After that I lose the ability to click on anything outside the window I have open and also the ability to click on much within the current window. For example I am in firefox and can write and send this. I can click on the + to open a new tab, I can click on any tab and scroll up and down, (when scrolling the scroll freezes for about 2 seconds and when it comes back there is no longer an ability to click), I can't click on File, Edit, View, History, Bookmarks, Tools, Help. I can't click on the down arrow to get a list of open tabs.

If I move the mouse over any of the menu buttons on the left of the screen they highlight and remain highlighted when I move the mouse away, I can't click on any of them.

Alt  Ctrl F6 get me to a TTY where I can log in, from here killing X or Xorg using kill PID or killall or pkill or running startx will all get me to a log in screen where the mouse works normally and where I can log in normally but having logged in the mouse fails in exactly the same way after about 25 seconds.

I have never seen this problem or anything like it any an all ideas most welcome.

Stripes

[Duncan Roe]

2 wild suggestions:

1. Unplug mouse, wait a bit, re-plug. Does it work for a bit?
(If it's a Wifi mouse, remove battery).

2. Try another mouse.

Cheers ... Duncan.

> --
> You received this message because you are subscribed to the Google Groups "mlug-au" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to mlug-au+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/mlug-au/CAEZu4cWR541Opc5SONmB-f6%3Dvr-5NjiFrEB-RSAFS%3Djh9edrcQ%40mail.gmail.com.

[Danny Robson]

On 15/5/21 11:38 pm, 'stripes theotoky' via mlug-au wrote:
> Gnome-shell [2488]: Attempting to run a JS callback during garbage
> collection. This is most likely caused by destroying a clutter actor or
> GTK widget with ::destroy signal detected or using the destroy(),
> dispose() or remove() vfuncts. Because it would crash the application,
> it has been blocked. The offending callback was SourceFunc()

It sounds like you're getting hit by
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868
Or something similar to it.

I took a brief look at some related bug reports and it sounds like it's
frequently related to one particular GNOME extension or application. If
you can figure out which one it is and uninstall/update it you might be ok.

You might be able to track down the offender by looking for a stack
trace or other related information in the logs near these errors. On
some examples I've seen it tends to happen only near the first instance
of the error.

Unfortunately I wasn't able to discover a workaround.

Cheers,
Danny Robson

[stripes theotoky]

2 wild suggestions:

1. Unplug mouse, wait a bit, re-plug. Does it work for a bit?

It is not related to the mouse. I have tried two mice, the touch pad and a wacom graphics tablet. I have disabled everything except the input device I am using so they can't be conflicting and the problem occurs with all of them. I have tried with them all enabled at the same time the problem is the same. I have for completeness tried all combinations of two of them enabled but with no change. Always about 5 min, the mouse click ability dies and the logs get flooded.

Thanks for the suggestions.

--

Stripes Theotoky

39°37'02.4"N 19°55'17.1"E

39.617334, 19.921417

 

[pushin.linux]

There could be a thermal overload issue. Maybe your CPU heatsink is, like mine was, clogged with dust. My mouse activity was erratic. Took my box down to the man with compressed air. 

Cheers

Andrew

Sent from my Galaxy

--
You received this message because you are subscribed to the Google Groups "mlug-au" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mlug-au+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mlug-au/CAEZu4cWfaOqu76Rb_DPAwAcNURyCnr25XUzpBbqQTQh6psc%3DLQ%40mail.gmail.com.

[stripes theotoky]

It sounds like you're getting hit by
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868
Or something similar to it.

Yes it plainly seems to be that and I have reported it there.

I took a brief look at some related bug reports and it sounds like it's
frequently related to one particular GNOME extension or application. If
you can figure out which one it is and uninstall/update it you might be ok.

So far as I know I have no gnome extensions installed at all.

You might be able to track down the offender by looking for a stack
trace or other related information in the logs near these errors. On
some examples I've seen it tends to happen only near the first instance
of the error.

I wouldn't even know where to begin with this.

Unfortunately I wasn't able to discover a workaround.

The workaround for me was very simple.

Exterminate all snap packages so there is no chance of having different versions of gnome-shell or GTK, and when that didn't fix it

sudo apt install ubuntu-mate-desktop^

Solved the problem totally. If anyone ever finds the problem with gnome and fixes it then I will probably go back to it but for now I have work to do and can't be wasting days fighting with this.

Thanks for the help.

Stripes

Cheers,
Danny Robson

--
You received this message because you are subscribed to the Google Groups "mlug-au" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mlug-au+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mlug-au/75a37ceb-75d3-1ade-a499-7b33c93bb1c7%40nerdcruft.net.

[stripes theotoky]

There could be a thermal overload issue.

Now that is a good idea that probably should be done in any case.

 

To view this discussion on the web visit https://groups.google.com/d/msgid/mlug-au/60a12d69.1c69fb81.2e6dc.1aeb%40mx.google.com.

[Darren Wurf]

Stripes, I don't have any advice, just wanted to say that you always have the most interesting problems! :(

Can you access menus in the browser using alt+f? Can you use the Ubuntu app bar by pressing the Super key (often the windows key)?

To view this discussion on the web visit https://groups.google.com/d/msgid/mlug-au/CAEZu4cXB3bj2JbU-Xnd-QOirxGoY4vcDYAqFb_j%3DCUBrH3o3cw%40mail.gmail.com.

[stripes theotoky]

On Mon, 17 May 2021 at 14:52, Darren Wurf <darre...@gmail.com> wrote:

Stripes, I don't have any advice, just wanted to say that you always have the most interesting problems! :(

No real point in having dull boring problems :-)

Can you access menus in the browser using alt+f? Can you use the Ubuntu app bar by pressing the Super key (often the windows key)?

No, when gnome-shell goes mad I lose pretty well everything except the ability to Alt Ctrl F6 to log in, read the logs shutdown etc from there.

I am now running the Mate desktop and I find the laptop is running much much cooler even with a heavier load on it so this must have been a problem for quite a long time.

I have left gnome installed so will periodically use it and see if the problem continues or if updates fix it.

Regards

Stripes

To view this discussion on the web visit https://groups.google.com/d/msgid/mlug-au/CAHhXpGa94%2BsX2PhEk_712SdOUWo-khWZvPUbgbdXMt-cYHcA9w%40mail.gmail.com.