mouse left+right button loosing function occasionally

[stubborn]

Please fill in this template when posting!
XMBC Version[^2.19.2]:
Installed or Portable version:[installed]
Windows Version[7+10]:
Mouse Information (brand/model)[independent from used mouse model/DELUX M525]:
Relevant Computer Information (CPU, RAM etc)[independent from used PCAMD Ryzen 5/32GB]:
Did the problem occur after an upgrade of XMBC? (If so, from what version?)[no]:
Did the problem occur after a Windows update/upgrade? (If so, from what version?)[no]:
How long have you used XMBC?[forever]:
What language and keyboard layout do you use in Windows?[english/german]:

Clear description of the problem:

i am not shure if thats a bug or a wrong setting in XMBC or if its managable from XMBC. i am using win10, but it appeared in win7 too. i was asking for support or an idea @forums of some of the other programs involved and could not get help since decades. this problem appeares occasionally since ~a decade?, with several versions of XMBC and other programs involved.

the following programs are involved:
foobar2000
total commander
opera browser
clipX (clipboard manager) (happended with other CB managers too)
xmouse button control
keepass 1/2
an of course XMBC

as i am having x00 tabs oben in opera i am listening to music, searching/editing/moving/creating files after some time the left and right button of the mouse stops working. when i click left or right buttons, the focussed window looses focus. mouse wheel click and other buttons continue working.

this only happens when foobar process was started. but i asked in their forum more than once and could not get help. sometimes mouse funcitonality comes back when i close XMBC or foobar or some of the other programs. or after some time passing.

i checked my settings for conflicts with other programs and noticed, the number of mouse lines for scrolling can be set at different places within windows. so there is a conflict, on window is set to 3 the other is set to 6. but this i believe cannot be the reason, since this seems new in win10.

the reoccuring error in XMBC is
"NewApplicationSettings: Ignoring mouse speed as XMBC is not allowed to change it"
this is occuring all the time/the log is full of this, even i dont change any settings inbetween. XMBCs settings for changing speed and dpi is unchecked.
there are no other errors in the log.

my quickest workaround is to switch user in win, but i have to close all open programs, otherwise some will be resized which is annoying. rebooting also works.

[stubborn]

with less insight i was posting this problem in a diffenrent setting before viewtopic.php?t=3800

[phil]

So you failed to mention, perhaps the most important thing... What you have set the left and right button to in XMBC - are they remapped, or are they left as "No Change (don't intercept)"?

If they have not been remapped, then I struggle to see any reason they can stop working, unless somehow windows thinks they have been stuck down (pressed and not released). Perhaps a copy of your settings file (save profile) might be useful as it will allow me to see all of your setup.

If that is the case, CTRL+ALT+DEL and then CANCEL normally fixes that (does it in this case when the buttons stop working?)
Does disabling XMBC and re-enabling it fix it? (You can setup a global hotkey to do this, or use the disable option on the XMBC context menu (tricky if the buttons aren't working!).

Now, I'm confused as the the tangent and talk about speed/dpi settings - is this another problem or just something you have spotted in the log (and completely unrelated to buttons not working)?

NewApplicationSettings: Ignoring mouse speed as XMBC is not allowed to change it

For starters, that is not an error... It just information, meaning that the setting: "Allow XMBC to set the mouse speed and DPI" on the pointer tab in settings, is not ticked. So XMBC refuses to make any mouse speed changes. If you want XMBC to be able to modify the cursor speeds, then you need to tick that box!

That shouldn't be a problem/error, unless of course, the checkbox IS ticked!

The foobar thing is interesting and rings a bell... There is a long standing workaround in XMBC for Foobar - maybe that needs looking at again (I cant even remember what it was working around!).

If you can reproduce this with debug logging turned on, it might be useful. If so, please make a note of the time that the buttons stop responding, then we (I) can look in the log and see if XMBC is seeing button messages or not. If it only happens occasionally, it might make it tricky to capture in the debug log. You can setup a global hotkey to toggle debugging on/off - then when it stops working, turn on debug, press the buttons a few times, and send the log.

[stubborn]

What you have set the left and right button to in XMBC - are they remapped, or are they left as "No Change (don't intercept)"?

they are left as "No Change (don't intercept) in any configuration. i just realized, at some configs there was the entry "layer 1" missing. dont know how that happended. never used multilayers and did not delete those entries.

i have profiles for ~20 programs set.

tried to attach a copy of my settings file. i get the error "File too large: ORANGE's XMBC Profile.xmbcp". but it is 786kb only

Ignoring mouse speed as XMBC is not allowed to change it

i have spotted that in the log. it is shown many times every day. not shure if its related. the mouse has an extra button to set dpi. i normaly dont touch that. there is no obvious problems with the dpi settings.

i turned debug loggin on just now. next time the error occurs i will post it.

CTRL+ALT+DEL and then CANCEL ....will remember that, thanx.

[phil]

OK, Not sure why that file is too large - will have to check the limits but that's not big!
But if you want to send it by other means (email for example) then do so to phil [at] highrez {dot) co [dot} uk

Be aware that debug logging turns itself off after XMBC restarts (i.e. you restart Windows etc!)
I've just added a neat little trick to the next build/release, which will buffer the last 80 debug log messages in memory, and when you turn on debug logging, it will flush that to the log file (so it will be able to show the last 80 debug messages, even if debug logging is off when the trouble happens, turning it on, should (hopefully) capture what was going on when it went wrong - not every debug message (as there are so many potentially irrelevant ones)!

[stubborn]

problem reoccurred. CTRL+ALT+DEL was not responding. fixed it via switch user. forgot to use global hotkey+debug log. will return when problem returns. send phil the log.

[phil]

Thanks, I'll take a look when I get a moment!

Stupidly, I forgot to mention, to make a note of the time the problem happens, there's 18,000+ lines of log in that file and finding a single line (that may or may not be there) without any indication of the time it went wrong is a little tricky!. Do you have any idea, even roughly? If not, can you repeat but make a note of the time the error occurs!

Actually the new version 2.20.2 might be of benefit here, as it buffers the last 80 debug log lines (even when debug logging is turned off) to memory, then when enabling debug logging it should flush that to the log file (so by enabling debug logging, the log file will automatically show the last 80 debug log messages! So in theory, with 2.20.2, you can leave debug logging OFF until it goes wrong, then turn on debug logging and send the log.
It's still <always> worth making a note of the time too!

Anyhow, I'll see if there is anything I can find

[stubborn]

time would be the last 30min before the end

[stubborn]

it happened again, just now. i disabled xmbc via hotkey. buttons still dont work. reanabled xmbc. no change. switched user. opened xmpc. debug logging was still on. the log shows new entries:

Code: Select all

04-03-2023 12:39:30.121> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP), X=956, Y=703, Data=0x00000000, Flags=0x00000000, Time=5620859, Info=0x0, Ptr=0x5980B1D, Layer=0
04-03-2023 12:39:30.121> ProcessButton: Detected active HWND changed from 0x0003068E to 0x00100A24 (profile window 0x0003068E, ProcID 8580). Getting process name...
04-03-2023 12:39:30.121> GetProcessIntegrityLevel for PID 8580 returned 0x00002000
04-03-2023 12:39:30.121> GetProcessName(3 ProcessButton): Got name for PID 8580, 'thunderbird.exe' using GetProcessImageFileName
04-03-2023 12:39:30.121> GetProcessName result 1 time 0ms
04-03-2023 12:39:30.121> FindAppSettings: Matching profile not found.
04-03-2023 12:39:30.121> ProcessButton: Profile/active app/window change (due to mouse button) from 'totalcmd.exe' to 'thunderbird.exe'.
04-03-2023 12:39:30.121> Enabling default button settings...
04-03-2023 12:39:30.121>   Layer 0: Left = ** No Change (Don't intercept) **, Right = ** No Change (Don't intercept) **, Middle = Simulated Keys, 4th = ** No Change (Don't intercept) **, 5th = ** No Change (Don't intercept) **, Scroll Up = ** No Change (Don't intercept) **, Scroll Down = ** No Change (Don't intercept) **, Tilt Left = ** No Change (Don't intercept) **, Tilt Right = ** No Change (Don't intercept) **
04-03-2023 12:39:30.121>   InvertScrolling=off InvertHorizontalScrolling=off ScrollPages=off SwapButtons=0
04-03-2023 12:39:30.121> NewApplicationSettings: Ignoring mouse speed as XMBC is not allowed to change it
04-03-2023 12:39:30.121> SPI is already lines: 3, state: 0 - no need for further change
04-03-2023 12:39:30.121> CLockAxis: Reset Cursor
04-03-2023 12:39:30.121> CSPIThread: Reset Cursor (TID 0x594)
04-03-2023 12:39:30.121> Translating Left Button Up Key state 0x1: Action 40 [** No Change (Don't intercept) **]
04-03-2023 12:39:30.121> SPIThread: Resetting cursors
04-03-2023 12:39:30.121> MouseHookLLProc: Passing original mouse message 00000202 through....
04-03-2023 12:39:37.551> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN), X=1294, Y=413, Data=0x00000000, Flags=0x00000000, Time=5628296, Info=0x0, Ptr=0x5980B1D, Layer=0

[stubborn]

again. since i cannot post all changes i just post the end of the log. ....no that does not make sense. the time stamps are late. i send you another email.

[phil]

So, I see a 5 second gap, at about 14:02:39 - 14:02:44
Is that were it stopeed working (Im gussing so as after the gap you tried disabling XMBC).

Code: Select all

04-03-2023 14:02:39.564> MouseHookLLProc: Passing original mouse message 00000201 through....
04-03-2023 14:02:39.718> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP), X=64, Y=1908, Data=0x00000000, Flags=0x00000000, Time=10610453, Info=0x0, Ptr=0x5980B1D, Layer=0
04-03-2023 14:02:39.718> Translating Left Button Up Key state 0x21: Action 40 [** No Change (Don't intercept) **]
04-03-2023 14:02:39.718> MouseHookLLProc: Passing original mouse message 00000202 through....
04-03-2023 14:02:44.202> Received global hotkey: 7
04-03-2023 14:02:44.202> Toggle Enable/Disable by global hotkey
04-03-2023 14:02:44.202> OnToggleDisable: Disable XMBC

I see also, that at 14:02:28 you left foobar2000 back to total commander...
And there is this in the log:
14:02:28.152> ProcessButton: Previous process was Foobar2000.exe. Enabled special 'fix up' mode for next button press/release.

I do wonder if this "special fix up" is the problem. Perhaps it is no longer relevant/required - I will need to research what it does and why (its going back, probably 15+ years!). But it seems, the next button is passed through (even though remapped) means maybe that button gets "stuck" down... Because the button up is "ignored" even though the button down was passed through... May well be relevant...

I think I need to install foobar2000 and total commander and try your settings. May get a chance to do so later today..

[stubborn]

thanx for looking into it. since the amount of code postable is limited here, i sent you the log and my settings per email. the log changed back in timeline maybe its best you look into the 2 logs i sent you.

you have been writing in 2018 already about that "special fix up". i could not know what that piece of code is doing. unfortunately, this error happens only occasionally, so you might be unlucky to reproduce it on your machine.

[phil]

OK I installed foobar/total commander and your settings... And I can reproduce this problem!
It seems the legacy fix for foobar is the cause - and maybe it is not needed any more. I will take it out and send you a test build to see how you get on... But maybe I need to make it optional rather than hard coded - the "fix" was put in to prevent the mouse buttons getting locked up / disabled in version 1.30 back in March 2007 (lol). I cant find any related forum posts from back then, the closest I found was in 2008 for 1.34....

[stubborn]

And I can reproduce this problem!

there is foobar v 2.0 out now, i think its written in a different language. but the error occurs there too.
will gladly try your test build. this has bugging me for so long

[phil]

email sent