Preventing usb mouse from waking computer 2

English Hardware
1

This is exactly the same issue as this thread:

https://forums.opensuse.org/t/preventing-usb-mouse-from-waking-computer/176865/6

That threat is closed so i created this one

I tryed to create a udev rule like in that thread, but Im still having issues with all the screens coming on when i mouse the mouse:

furryone@PC-OS2:~> lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 04ca:0020 Lite-On Technology Corp. USB Keyboard
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 2109:2813 VIA Labs, Inc. VL813 Hub
Bus 001 Device 005: ID 0d49:7310 Maxtor OneTouch 4
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 007: ID 1058:1140 Western Digital Technologies, Inc. My Book Essential (WDBACW)
Bus 001 Device 008: ID 2109:2813 VIA Labs, Inc. VL813 Hub
Bus 001 Device 009: ID 1058:2627 Western Digital Technologies, Inc. My Passport 2627
Bus 001 Device 010: ID 1058:2627 Western Digital Technologies, Inc. My Passport 2627
Bus 001 Device 011: ID 1532:0064 Razer USA, Ltd Basilisk
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 1058:2622 Western Digital Technologies, Inc. Elements SE 2622
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 005: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 004: ID 1058:1230 Western Digital Technologies, Inc. My Book (WDBFJK)
Bus 004 Device 005: ID 1058:1140 Western Digital Technologies, Inc. My Book Essential (WDBACW)
Bus 004 Device 007: ID 1058:1235 Western Digital Technologies, Inc. My Book (WDBFJK0040HBK)
Bus 004 Device 008: ID 1058:25fe Western Digital Technologies, Inc. Elements SE 25FE
furryone@PC-OS2:~>

I then created the udev rule file “90-mouse.rules” in /etc/udev/rules.d/

ACTION==“add”, SUBSYSTEM==“usb”, DRIVERS==“usb”, ATTRS{idVendor}==“1532”, ATTRS{idProduct}==“0064”, ATTR{power/wakeup}=“disabled”

however moving the mouse still wakes up all the monitors
It’s a usb basillica mouse

Help appreciated :slight_smile:

2

Have you rebooted the computer or reattached the mouse after creating the rule?

3

Yes, i have re-booted the PC
makes no differance

4

“Waking computer” and “waking monitors” are two entirely different things. You need to clarify what is your goal.

5

What do you mean ?
I already provided a previous link to the exact same issue i have above
I stated that this is about “monitors” not PC’s

6

I mean that the title of this topic says “waking computer” and the body of this topic says “waking monitor”.

7

And the other thread says “which will wake the computer from sleep”

So when in your case the monitor lights up again after going dark because of inactivity, then that is definitely not “exact the same issue” as in the other thread where a computer (PC) wakes up after being put into “sleep” (or suspend to RAM).

8

Im sorry that there was confusion here

This is the method i use in KDE Plasma to turn the screens/monitors off

Settings > Shortcuts > KDE Power Management System

Turn Off Screen: CTRL + Down Arrow

This works 100% fine at turning all the screens/monitors off
However, there is a small issue that a percentage of people have noticed which is that after
an unpredictable amount of time the screens/monitors all turn back on again
“Presumably” this is from some type of event that has not been officially tracked down

monitor is randomly powered back on

https://bugs.kde.org/show_bug.cgi?id=348082

I created my own hypothesis/conjecture about why this might happen:

TEST:

KDE PLASMA: 6.1.2

I disconnected my usb mouse for about 24 hours
I had all my screens/monitors turn off via my shortcut of CTRL + Down Arrow setup in shorcuts

After 24 Hours, i notived that all my screens/monitors were all still turned off

HYPOTHESIS: The mouse sensitivity is very very high, and and random/intermittant times either the X or Y axist will still get triggered,
however, these X/Y mouse movements do not have any visual effect on the screen mouse pointer/cursor, because (hypothetically) it’s possible that at least one of the axis’s
(X or Y) is constantly in fluctuation back and forth between 2 different values (maybe non-integer values)
IF this is in fact the case, then the DE packages responsible for on-screen mouse/pointer movement, will have a certain level of calibration setup to take both
on-screen mouse pointer/curser stability into account while also taking the mouse mouse DPI/Sensitivity and (optionally the mouse acceleration) into account as well
The stability would require a minimum threshold number of either fractial or integer values to be reached for either/both X and Y axist’s BEFORE any actual DE on-screen mouse pointer
movement would take place.
Variance BELOW this minimum threshold would be what potentially triggers the screen to come back on as an official “Event”

        The other method that could hypothetically be used for DE mouse pointer/cursor stability is to have a minimum amount of time/delay (in say, ns or ms) be met/made "between"
        mouse pointer X/Y axis movements before the DE on-screen mouse pointer/cursor actually moves

Googling resulted in me coming accross the first link - which at least appears to me to be about screen/monitors being awakened e.g. " [Preventing usb mouse from waking

“preventing-usb-mouse-from-waking-computer” - I was sure by the description in here, that he was referring to monitors/screens

I tryed to reproduce what appears to be a valid solution here using a udev rule, but without success

9

No surprise as you completely misunderstood what that other thread was about.

And I am sorry to say, but the description of what you did and what you expected and what happened instead should have been made in your first post. :frowning:

Specially the fact that you switch the monitor off by an action instead of letting it happen by inactivity. All deviations from default that may have to do with a problem should be mentioned. Most people will not handle their systems like you and also they are not clairvoyant.

And that brings me to a question. Have you switched off in KDE > Systemsettings > Energy Saving > the Screen Switch off?.
Because you say that after 24 hours the screen is on again, but even when it was switched on sometime during that 24 hours by a minimal mouse action, it then should have been switched off again “automatic” after the Switch off timeout (normally 10 mins).

10

No surprise as you completely misunderstood what that other thread was about.

And I am sorry to say, but the description of what you did and what you expected and what happened instead should have been made in your first post. :frowning:

Specially the fact that you switch the monitor off by an action instead of letting it happen by inactivity. All deviations from default that may have to do with a problem should be mentioned. Most people will not handle their systems like you and also they are not clairvoyant.

And that brings me to a question. Have you switched off in KDE > Systemsettings > Energy Saving > the Screen Switch off?.
Because you say that after 24 hours the screen is on again, but even when it was switched on sometime during that 24 hours by a minimal mouse action, it then should have been switched off again “automatic” after the Switch off timeout (normally 10 mins).

You have not quoted what i said
I can quote fine here
You: “Because you say that after 24 hours the screen is on again”
Me: “After 24 Hours, i noticed that all my screens/monitors were all still turned off”

“And that brings me to a question. Have you switched off in KDE > Systemsettings > Energy Saving > the Screen Switch off?.”
KDE Settings > Power management

  • Display and Brightness: Turn off Screen: “Never”

“All deviations from default that may have to do with a problem should be mentioned.”

  • I never said that what i wanted was something that was a kde default setting
    All i said is that a udev option i tryed did not appear to work - and i DID post a terminal output - something you have not referenced here either

You have made no reference to the KDE Bug Report i posted
You have made no reference to my Hypothesis either

Someone in one of the groups on matrix.org claims that kde has no option to turn off input events for things like mouse movement or mouse buttons to have the screens/monitor turned on again

So, that why i saw that until this issue is fixed (noting my hypothesis about the cause) that a work-around would be the only option - and no one has suggested 1 possibility so far

11

You’re failing to correctly quote. Check your inbox messages, @discobot must want to teach you how to do it correctly.

The udev rule is for suspended power state, it holds no relation with what you want.

Now that you really said what you want. As workarounds, you can:

  • unplug mouse; or
  • turn off the monitor through its power button.
12

Oi! Para descobrir o que eu posso fazer, diga “@discobot exibir ajuda”.

13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.