X-Mouse Button Control doesn't work after awakening

x64 Replacement/Alternative to Microsoft's IntelliMouse application.
Forum rules
Please read the forum rules before posting for the first time.
The more information you can provide, the quicker and more accurately someone can help.
NOTE: To reduce spam, new users can not post links or images until they have at least 4 posts.
prec
New User
Posts: 5
Joined: Tue Oct 10, 2017 1:10 pm

X-Mouse Button Control doesn't work after awakening

Post by prec »

If I hybernate my Windows 10 (Windows 10 Home Italian - v. 1703 - build 15063.608), sometimes when I awake my PC X-Mouse Button Control (v. 2.16.1) is not working anymore. I have to kill it using task manager and restart the app. Older versions are ok.

User avatar
phil
Site Admin
Posts: 6695
Joined: Sun Apr 06, 2003 11:12 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by phil »

OK I'll take a look - thanks.
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 500Gb NVME, 2x2TB WD Black (RAID1)

User avatar
phil
Site Admin
Posts: 6695
Joined: Sun Apr 06, 2003 11:12 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by phil »

I wonder if you could help me with this as I am enable to reproduce it here.
Can you turn on debug logging (Advanced settings logging tab) and then OK/Apply that.
Then hibernate and resume and try and capture the problem.

Once captured, send me the debug log (and turn off debug logging again)?

Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 500Gb NVME, 2x2TB WD Black (RAID1)

prec
New User
Posts: 5
Joined: Tue Oct 10, 2017 1:10 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by prec »

I tried to use the activate the verbose log but I can't find the file after my PC restarted ... I'll have further tests in next days.

This is another log file, the one in \Users\xxx\AppData\Roaming\Highresolution Enterprises\XMouseButtonControl : https://drive.google.com/file/d/0B3rO-- ... sp=sharing

I miss to tell you I use external mouse on my notebook and I disconnect and reconnect it before and after sleep mode (sometimes during the sleep, sometimes before or after)

ResidentR6
New User
Posts: 2
Joined: Fri Oct 27, 2017 4:45 am

Re: X-Mouse Button Control doesn't work after awakening

Post by ResidentR6 »

Same thing, Windows 7 russian. After hibernate and wake up it does not override mouse behavior and does not respond to mouse on tray icon. Need to be restarted though task manager.

I'll try to make a log. Previous versions did not tested. Accent: I had reduced priority form RealTime to BelowAverage. Now I've returned realtime, trying if it helps...

CONFIRMED: with RealTime priotity there's no such bug. At least, I didn't catch it anymore in same conditions.
Trying to acquire a log with BelowAverage priority...
And got nothing, it works. May be it has to pass some time (hours) before wake up? Left log flag, may be the bug shows itself later.

___________
+Other small bug: when log flag set, it's shown "not set" after application restart. But it still set, log is written.

User avatar
phil
Site Admin
Posts: 6695
Joined: Sun Apr 06, 2003 11:12 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by phil »

Hi all, unfortunately, one of the side effects of enabling debug logging (if that';s what you did) is that it slows things in XMBC down (as it takes longer to write more log to disk). So if this "bug" is related to timing (as would be suggested by modifying the process priority) then changing anything could be enough to have an impact.

What is the spec of your machine (how many CPUs, how fast etc. is it a bit old, or a super duper band new thing)? I have a mix of specs from I7 down to I3 and dont seem to have this problem on any of my machines (although I only hibernate my older/slower laptop & media PC on a regular basis).

That of course makes it rather difficult for me to track down and fix :(.
There have been instances of this problem in the past. XMBC now resets itself when resuming from hibernate - so I dont understand why this problem can still happen but there must be something that I've missed.
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 500Gb NVME, 2x2TB WD Black (RAID1)

prec
New User
Posts: 5
Joined: Tue Oct 10, 2017 1:10 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by prec »

CPU: AMD A6-5200 APU with Radeon HD Graphics 2.00 Gb
RAM: 8 Gb
Windows 10 Home 64 bit ita
HD: 500 Gb

PC is fast enough, I have thousand of heavy programs running (XAMPP, 100 chrome tabs, edge, explorer, skype, office, github desktop, acrobat, teamviewer and a lot of utilities running all toghether) and they awake without problems after sleep or hibernate. Consider the program is "dead" after awakening it: if i left click or right click on its icon in my tray bar nothing happens, I have to kill it and restart it.

prec
New User
Posts: 5
Joined: Tue Oct 10, 2017 1:10 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by prec »

By the way, in your log file I see some alerts as "Hook thread did not exit in a timely fashion!", "Warning: Low Level Hook Timeout is low. If you have problems try increasing this value.", "RemoveMouseHook took 10344ms" (10 seconds?!?)

Are you sure your verbose log can't help?

Code: Select all

25-10-2017 19:20:55.0984> Translating Left Button Up Key state 0x1: Action 40 [** No Change (Don't intercept) **]
25-10-2017 19:20:55.0984> MouseHookLLProc: Passing original mouse message 00000202 through....
25-10-2017 19:20:56.0640> KeyHookLLProc: ALT (0xA4) released, Started 200ms KeySwitchTimer ID: 0x00000000
25-10-2017 19:20:56.0765> GetProcessIntegrityLevel for 0x00000528 returned 0x00002000
25-10-2017 19:20:56.0765> GetProcessName(7 WindowFromHWND): Got name for PID 3872, 'explorer.exe' for HWND 0x00101B62 using GetProcessImageFileName
25-10-2017 19:20:56.0765> GetProcessName result 1 time 0ms
25-10-2017 19:20:56.0843> KeySwitchTimerProc: Checking active app profile...
25-10-2017 19:20:56.0843> GetProcessIntegrityLevel for 0x000003A4 returned 0x00002000
25-10-2017 19:20:56.0843> GetProcessName(2 Keyboard): Got name for PID 4232, 'notepad++.exe' for HWND 0x00160AA0 using GetProcessImageFileName
25-10-2017 19:20:56.0843> GetProcessName result 1 time 0ms
25-10-2017 19:20:56.0843> Detected new HWND 00160AA0 (due to keyboard) from 00101B62. The active profile has not changed.
25-10-2017 19:20:57.0593> GetWindowCaption: WM_GETTEXTLENGTH returned 24476 which is too long to be a caption!
25-10-2017 19:20:57.0750> GetWindowCaption: WM_GETTEXTLENGTH returned 24476 which is too long to be a caption!
25-10-2017 19:20:57.0906> GetWindowCaption: WM_GETTEXTLENGTH returned 24476 which is too long to be a caption!
25-10-2017 19:20:58.0781> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:08.0875> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:08.0031> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:09.0187> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:09.0343> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:13.0593> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:13.0750> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:13.0906> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:14.0062> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:14.0218> GetWindowCaption: WM_GETTEXTLENGTH returned 24477 which is too long to be a caption!
25-10-2017 19:21:14.0937> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN), X=63, Y=53, Data=0x00000000, Flags=0x00000000, Time=722933937, Info=0x0, Ptr=0x3A0135F, Layer=0
25-10-2017 19:21:14.0937> Translating Left Button Down Key state 0x0: Action 40 [** No Change (Don't intercept) **]
25-10-2017 19:21:14.0937> MouseHookLLProc: Passing original mouse message 00000201 through....
25-10-2017 19:21:14.0046> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP), X=63, Y=53, Data=0x00000000, Flags=0x00000000, Time=722934046, Info=0x0, Ptr=0x3A0135F, Layer=0
25-10-2017 19:21:14.0046> Translating Left Button Up Key state 0x1: Action 40 [** No Change (Don't intercept) **]
25-10-2017 19:21:14.0046> MouseHookLLProc: Passing original mouse message 00000202 through....
25-10-2017 19:21:35.0796> Display resolution changed (1366, 768)
25-10-2017 19:22:11.0531> Power State: System is suspending operation.
25-10-2017 19:22:12.0125> Reinstall mouse hook on resume is enabled. Remove hook before suspending...
25-10-2017 19:22:12.0500> HookThread: Finished the message loop. Cleaning up...
25-10-2017 19:22:12.0500> Removing keyboard hook...
25-10-2017 19:22:12.0500> Removing any active XMBCHook Timers...
25-10-2017 19:22:12.0500> Removing mouse hook...
25-10-2017 19:22:12.0500> Unable to enter critical section for lock 'KillTimers' (TID: 00003C78) because it is already locked by 'HookThread Clean-up' - Waiting...
25-10-2017 19:22:17.0390> Hook thread did not exit in a timely fashion!
25-10-2017 19:22:22.0390> Timer thread did not exit in a timely fashion!
25-10-2017 19:22:22.0390> RemoveMouseHook took 10000ms
25-10-2017 19:22:22.0468> Unable to enter critical section for lock 'GetHooked' (TID: 0000451C) because it is already locked by 'HookThread Clean-up' - Waiting...
25-10-2017 19:22:30.0984> Unable to enter critical section for lock 'SetDebug' (TID: 0000451C) because it is already locked by 'HookThread Clean-up' - Waiting...

*******************************************************************************************************************************************
26-10-2017 11:07:47.0046> X-Mouse Button Control v2.16.1 (x64) Startup. Commandline ''
26-10-2017 11:07:56.0703> Running in high integrity mode (0x00003000)
26-10-2017 11:07:56.0718> Loaded 0 application specific profiles (0 normal and 0 custom window).
26-10-2017 11:07:56.0718> Running on Microsoft Windows 10 Home Edition (build 15063), 64-bit, Hook Timeout: 200 ms
26-10-2017 11:07:56.0718> Warning: Low Level Hook Timeout is low. If you have problems try increasing this value.
26-10-2017 11:07:56.0718> Startup folder: 'C:\Program Files\Highresolution Enterprises\X-Mouse Button Control\'
26-10-2017 11:07:56.0718> Settings (and log) folder: 'C:\Users\Enzo\AppData\Roaming\Highresolution Enterprises\XMouseButtonControl\'
26-10-2017 11:07:56.0734> Using keyboard language 0x04090409
26-10-2017 11:08:06.0000> You are using the latest available version of X-Mouse Button Control.
26-10-2017 18:01:29.0656> Power State: System is suspending operation.
26-10-2017 18:01:29.0968> Reinstall mouse hook on resume is enabled. Remove hook before suspending...
26-10-2017 18:01:30.0812> Removing any active XMBCHook Timers...
26-10-2017 18:01:35.0625> Hook thread did not exit in a timely fashion!
26-10-2017 18:01:40.0625> Timer thread did not exit in a timely fashion!
26-10-2017 18:01:40.0625> RemoveMouseHook took 10344ms


User avatar
phil
Site Admin
Posts: 6695
Joined: Sun Apr 06, 2003 11:12 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by phil »

I didn't say it cant help, I said (to ResidentR6) that it might affect timing and cause the problem to stop occurring. Its still very much worth trying!

As to the two you picked out, RemoveMouseHook shouldn't be a real problem if it takes a long time (other than it means probably that there is a lot of other things going on at the same time).

However, the other two I would be more concerned about.
1. Warning: Low Level Hook Timeout is low. If you have problems try increasing this value
This means that the hook can timeout and be removed, causing XMBC to stop working (until you disable/enable or restart). Adjusting this may well fix your problem. You can adjust the timeout in the advanced settings tab (and you can see what it is currently set to). I tend to go somewhere between 2 seconds and 5 seconds (2000-5000ms). Be aware that other applications can change this value (and some <volume2> change it without warning to inappropriate values which is really annoying!).

2. Hook thread did not exit in a timely fashion...
Probably related to "RemoveMouseHook took 10344ms" its effectively the same thing being reported from two places (where it tries to kill the thread) and in the thread. I wouldn't be so concerned about these.

Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 500Gb NVME, 2x2TB WD Black (RAID1)

ResidentR6
New User
Posts: 2
Joined: Fri Oct 27, 2017 4:45 am

Re: X-Mouse Button Control doesn't work after awakening

Post by ResidentR6 »

The bug happened again
28-10-2017 15:00:59 - it's a moment when I sent a computer to Hibernate. It means XMBC tries to do something when the OS activlely turns down all the hardware, stops dispatcher and writes all memory to Hibernate file.

When 28-10-2017 22:40 the OS woke up, nothing new added to log. XMBC does not hook mouse, does not respond to clicks on it's icon, and has to be killed manually by task manager.

I think, it'n not a good idea to do anything after the start of hibernating. If something need to be done, better way to do it exactly in the handler that responds to the OS that XMBC allows the OS to go sleep - in this case the OS is free of hard tasks.

Here is a log:
*******************************************************************************************************************************************
27-10-2017 08:18:35.0815> X-Mouse Button Control v2.16.1 (x86) Startup. Commandline '/notportable'
27-10-2017 08:18:35.0862> Running in high integrity mode (0x00003000)
27-10-2017 08:18:35.0862> Loaded 0 application specific profiles (0 normal and 0 custom window).
27-10-2017 08:18:35.0862> Running on Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 32-bit, Hook Timeout: 3000 ms
27-10-2017 08:18:35.0862> Startup folder: 'C:\Program Files\X-Mouse Button Control\'
27-10-2017 08:18:35.0862> Settings (and log) folder: 'C:\Users\Олег\AppData\Roaming\Highresolution Enterprises\XMouseButtonControl\'
27-10-2017 08:18:35.0862> Using keyboard language 0xF0C00419
27-10-2017 08:18:42.0428> Power State: System is suspending operation.
27-10-2017 08:18:42.0428> Reinstall mouse hook on resume is enabled. Remove hook before suspending...
27-10-2017 08:18:42.0444> Removing any active XMBCHook Timers...
27-10-2017 08:18:42.0460> CSendInput: Exiting SendInput thread.
27-10-2017 08:18:42.0460> Hook thread exited with error code 0.
27-10-2017 08:18:42.0460> Timer thread exited with error code 0.
27-10-2017 08:20:18.0681> Power State: Operation resuming automatically after event.
27-10-2017 08:20:18.0681> Reinstall mouse hook on resume is enabled. Re-hooking mouse...
27-10-2017 08:20:19.0071> Loaded 0 application specific profiles (0 normal and 0 custom window).
27-10-2017 08:20:20.0820> Using keyboard language 0xF0C00419
27-10-2017 08:21:10.0614> CMyMessageWnd::OnSetup - Opening setup dialog.
27-10-2017 08:21:10.0660> Loaded 0 application specific profiles (0 normal and 0 custom window).
27-10-2017 08:22:18.0724> You are using the latest available version of X-Mouse Button Control.
27-10-2017 08:32:41.0058> CMyMessageWnd::OnSetup - Setup dialog closed.
27-10-2017 08:32:41.0074> Loaded 0 application specific profiles (0 normal and 0 custom window).
27-10-2017 08:32:46.0097> You are using the latest available version of X-Mouse Button Control.
27-10-2017 09:23:03.0703> JigglerTimerProc: No activity for some time. Re-enabling inactivity timer.
27-10-2017 13:56:17.0458> JigglerTimerProc: No activity for some time. Re-enabling inactivity timer.
27-10-2017 14:32:46.0136> You are using the latest available version of X-Mouse Button Control.
27-10-2017 15:27:02.0033> JigglerTimerProc: No activity for some time. Re-enabling inactivity timer.
27-10-2017 15:51:44.0589> Power State: System is suspending operation.
27-10-2017 15:51:44.0589> Reinstall mouse hook on resume is enabled. Remove hook before suspending...
27-10-2017 15:51:44.0589> Removing any active XMBCHook Timers...
27-10-2017 15:51:45.0760> CSendInput: Exiting SendInput thread.
27-10-2017 15:51:45.0916> Hook thread exited with error code 0.
27-10-2017 15:51:45.0916> Timer thread exited with error code 0.
27-10-2017 15:51:45.0916> RemoveMouseHook took 327ms
27-10-2017 16:08:00.0546> Power State: Operation resuming automatically after event.
27-10-2017 16:08:00.0546> Reinstall mouse hook on resume is enabled. Re-hooking mouse...
27-10-2017 16:08:00.0578> Loaded 0 application specific profiles (0 normal and 0 custom window).
27-10-2017 16:08:02.0668> Using keyboard language 0xF0C00419
27-10-2017 16:10:00.0558> You are using the latest available version of X-Mouse Button Control.
27-10-2017 17:00:53.0248> JigglerTimerProc: No activity for some time. Re-enabling inactivity timer.
27-10-2017 20:34:54.0065> JigglerTimerProc: No activity for some time. Re-enabling inactivity timer.
27-10-2017 22:10:00.0566> You are using the latest available version of X-Mouse Button Control.
28-10-2017 01:01:57.0520> JigglerTimerProc: No activity for some time. Re-enabling inactivity timer.
28-10-2017 04:10:01.0213> You are using the latest available version of X-Mouse Button Control.
28-10-2017 07:48:08.0199> JigglerTimerProc: No activity for some time. Re-enabling inactivity timer.
28-10-2017 10:10:01.0862> You are using the latest available version of X-Mouse Button Control.
28-10-2017 10:30:26.0359> JigglerTimerProc: No activity for some time. Re-enabling inactivity timer.
28-10-2017 15:00:59.0573> Power State: System is suspending operation.
28-10-2017 15:00:59.0636> Reinstall mouse hook on resume is enabled. Remove hook before suspending...
28-10-2017 15:01:00.0760> Removing any active XMBCHook Timers...
28-10-2017 15:01:04.0643> Hook thread did not exit in a timely fashion!
28-10-2017 15:01:11.0320> Timer thread did not exit in a timely fashion!
28-10-2017 15:01:11.0320> RemoveMouseHook took 11684ms

User avatar
phil
Site Admin
Posts: 6695
Joined: Sun Apr 06, 2003 11:12 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by phil »

I think, it's not a good idea to do anything after the start of hibernating. If something need to be done, better way to do it exactly in the handler that responds to the OS that XMBC allows the OS to go sleep - in this case the OS is free of hard tasks.
I dont know what you mean by "do it exactly in the handler that responds to the OS that XMBC allows the OS to go sleep"

Firstly, I had to add code to XMBC to disable/re-enable over hibernate/sleep, because often, when restarting after a hibernate, the windows hooks imply stopped working.

Secondly, this problem is very rare (it does not happen to many people so there is probably something else conflicting, or a particular setting that is causing the problem (have you sent me your XMBC settings file yet, I cant remember). As I said before, as this is rare, finding the bug (if its even in XMBC) will be tricky/impossible without debug log and even then, will still not be an easy one).

Thirdly, removing hooks and disabling XMBC should NOT stop it responding to right clicks on the system tray icon - so the fact that that is happening tells me that something more serious has gone wrong, like its stuck in a loop or something.

When this happens, what is the CPU Usage for the XMouseButtonControl.exe process (for example is it taking 100% of one core (so 25% of all if you have a quad core system)?

You can already disable the "remove hooks on hibernate/resume" by setting <ReinstallHook Disable="true" /> in the settings file (there is no GUI option for this, you have to edit the XML yourself I'm afraid! That might alleviate the problem, but equally, could make it worse - you may find that you cant click anywhere if the mouse hook remains active if XMBC still locks up, or you might find simply that the hook stops working across hibernate (which is what happened before I added the restart hooks when hibernating).

It is interesting that it went wrong after the log messages:
28-10-2017 15:01:04.0643> Hook thread did not exit in a timely fashion!
28-10-2017 15:01:11.0320> Timer thread did not exit in a timely fashion!

And it didn't go wrong at an earlier sleep/hibernate when those log messages didn't come out - that might give some clues, perhaps its already locked up at that stage... Also the line "CSendInput: Exiting SendInput thread." does not occur when it goes wrong - so i hasn't cleaned up properly.. the question is why!
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 500Gb NVME, 2x2TB WD Black (RAID1)

User avatar
phil
Site Admin
Posts: 6695
Joined: Sun Apr 06, 2003 11:12 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by phil »

Looking at Prec's debug log I think has answered the questions....

Code: Select all

24-10-2017 16:05:09.0906> Power State: System is suspending operation.
24-10-2017 16:05:09.0984> Reinstall mouse hook on resume is enabled. Remove hook before suspending...
24-10-2017 16:05:09.0015> HookThread: Finished the message loop. Cleaning up...
24-10-2017 16:05:09.0015> Removing keyboard hook...
24-10-2017 16:05:09.0015> Removing any active XMBCHook Timers...
24-10-2017 16:05:09.0015> Unable to enter critical section for lock 'KillTimers' (TID: 000026C4) because it is already locked by 'HookThread Clean-up' - Waiting...
24-10-2017 16:05:09.0015> Removing mouse hook...
24-10-2017 16:05:14.0015> Hook thread did not exit in a timely fashion!
24-10-2017 16:05:19.0015> Timer thread did not exit in a timely fashion!
24-10-2017 16:05:19.0015> RemoveMouseHook took 10000ms
24-10-2017 16:05:19.0218> Unable to enter critical section for lock 'GetHooked' (TID: 00003D08) because it is already locked by 'HookThread Clean-up' - Waiting...
24-10-2017 16:05:29.0843> Unable to enter critical section for lock 'SetDebug' (TID: 00003D08) because it is already locked by 'HookThread Clean-up' - Waiting...
The last line, after resume I think is where it locks up - forever. And this has happened because the threads have been killed while locked, thus never unlocked... I should be able to do something about that!
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 500Gb NVME, 2x2TB WD Black (RAID1)

User avatar
phil
Site Admin
Posts: 6695
Joined: Sun Apr 06, 2003 11:12 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by phil »

OK I think I have fixed it - try 2.17 Beta 11 to see if I have (or not) and let me know.
The beta will be available here later today: viewtopic.php?f=6&t=2625
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 500Gb NVME, 2x2TB WD Black (RAID1)

prec
New User
Posts: 5
Joined: Tue Oct 10, 2017 1:10 pm

Re: X-Mouse Button Control doesn't work after awakening

Post by prec »

Just installed latest beta version, I'll update you if this error still happens.

isandybridge
New User
Posts: 3
Joined: Thu Feb 04, 2021 7:27 am

Re: X-Mouse Button Control doesn't work after awakening

Post by isandybridge »

Hello,

I am using v2,19.2 on Windows 10 Pro and I have the same issue, after waking up X-Mouse Button Control no longer works, no only the config but the app itself can no longer be accesed, it seems to be frozen.

Can you check if the fix discussed in this thread maybe got lost between versions ?

Thank You.

Post Reply