OpenTabletDriver / OpenTabletDriver/OpenTabletDriver
Tablet stops working after resuming from suspend
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.1k
- Forks
- 534
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 12
Description
Steps to Reproduce
- Start OpenTabletDriver service, plug tablet and confirm that it's working
- Suspend the system
- Resume
Expected Behavior
Tablet should work as normal.
Observed Behavior
Tablet stops working. Cursor doesn't move when using the stylus. Buttons do not work.
Tablet LED lights up when stylus comes into contact but nothing happens on the screen.
OpenTabletDriver GUI tool still detects the tablet, but it still does not work even after changing and applying settings.
Additional behavior:
Running otd detect in the terminal yields:
Thg 1 05 20:13:11 kpc otd-daemon[102978]: [Device:Debug] A device stream was disposed.
Thg 1 05 20:13:11 kpc otd-daemon[102978]: [IPC:Debug] Disconnected from a client.
After searching for tablets
Manually running Detect tablet from the GUI fixes the issue
Unplugging the tablet and replugging fixes the issue
Tablet Device
Gaomon 1060Pro
Diagnostic Information
Acknowledgements
- I have installed OpenTabletDriver by following its official installation instructions.
- I have checked the OpenTabletDriver Wiki and respective FAQ pages, and my issue was not covered or actually fixed.
- I have searched the existing issues and this new issue is not a duplicate of any.
- I have written a concise and meaningful title.
- I am on the latest version of OpenTabletDriver.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with a Gaomon 1060Pro by starting OpenTabletDriver, suspending and resuming the system, then compare the behavior with manually running otd detect or using Detect tablet in the GUI. Trace the reported “A device stream was disposed” and client-disconnection messages; done means the tablet works after resume without unplugging or manually detecting it again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100