mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-25 23:35:58 +03:00
[GH-ISSUE #91] keylogger stops logging after some time #37
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DragonzMaster on GitHub (May 6, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/91
i setup a client and tested it
the keylogger was working great but unfortunately it suddenly stopped working after 30 min aprox. and just log the windows title and blank line under it
this is an attachment shows the problem
@yankejustin commented on GitHub (May 6, 2015):
Did your keyboard disconnect? My first thought would be that the Keylogger was attempting to get the state of a keyboard that was invalid.
Was the client built with any non-default or unusual settings?
@DragonzMaster commented on GitHub (May 6, 2015):
no it's laptop's keyboard so it can't be diconnected
and its setting was the default which came with it i have just changed the host to "127.0.0.1"
and the keylogger didn't work again until i have reopen it
@yankejustin commented on GitHub (May 6, 2015):
Run the client in debug mode and please tell me if an exception is raised in the output window.
@DragonzMaster commented on GitHub (May 6, 2015):
i tried debug mode but it seems that the client don't connect to the server correctly :/
@yankejustin commented on GitHub (May 6, 2015):
If I leave the keylogger on for 30 minutes, would I experience the same troubles?
@DragonzMaster commented on GitHub (May 7, 2015):
i don't know but that which happened with me and the Pic above shows what happened
@ghost commented on GitHub (May 7, 2015):
Are you using the latest solution? Do you use alt + tab to switch between applications?
@vigneshkarthisan commented on GitHub (May 7, 2015):
Do you have an external monitor setup?. MSDN says
GetAsyncKeyState()method won't work if current desktop is not the primary desktop.@DragonzMaster commented on GitHub (May 7, 2015):
yes i am using the latest solution and using ALT+Tab to switch
and i am working on only 1 monitor
@ghost commented on GitHub (May 7, 2015):
It looks like theres a problem writing the file somewhere
@vigneshkarthisan commented on GitHub (May 7, 2015):
There wouldn't be a problem writing to file, because the window titles are logged.
@ghost commented on GitHub (May 7, 2015):
There might be, not because of that, but when I ran a client, it never even created a new file after had running it for a few minutes
Edit: woops lol.. didn't enable it in the settings haha
@ghost commented on GitHub (May 7, 2015):
@DragonzMaster, are you able to recreate this problem again after it had first happened?
@vigneshkarthisan commented on GitHub (May 7, 2015):
Was the problem solved?
@yankejustin commented on GitHub (May 7, 2015):
Certainly not the external monitor. I have multiple monitors and have had no issues with this. I hooked up my laptop to another monitor (Windows 7) and it had no issues like this. Unfortunately I don't have free time now to leave it logging keys for at least 30 minutes. Maybe tomorrow!
@yankejustin commented on GitHub (May 7, 2015):
As @d3agle asked, I am curious if this showed again or if it was a one-time issue...
@ghost commented on GitHub (May 7, 2015):
Ok, so, this problem has happened with me as well. Ran the client on my host and let it run while I played some games etc.. I can't pinpoint exactly how long it took for the logs to stop working, but eventually it stopped logging the keys and kept logging the Window titles. I'm going to implement your suggestion @yankejustin with the time of the logs in the window title header, from when its first created and see if I can pinpoint what might be happening
@ghost commented on GitHub (May 7, 2015):
Here is what is happening, if someone wants to fix
Object null reference, k is null
This seems to happen after a certain amount of time, not sure why
@MaxXor commented on GitHub (May 7, 2015):
Can you confirm it's fixed with the latest commit?
@ghost commented on GitHub (May 7, 2015):
I left it running for ~2 hours and no problems
@ghost commented on GitHub (May 7, 2015):
Prior to the null check, it would null out around 30 minutes into the client being ran. It happened twice, around the same time, not sure why it was.
@ghost commented on GitHub (May 7, 2015):
Now to think of it though, it was probably a dead-key. The FromKeys method will return a null instead of a character, so that was probably why
@DragonzMaster commented on GitHub (May 7, 2015):
sorry guys i was sleeping as i see there is someone else faced this problem
and unfortunately when i run the debug release the client don't connect to the server (commit 311)
so i can't know if there is any exception thrown
@ghost commented on GitHub (May 7, 2015):
The problem is fixed now
@DragonzMaster commented on GitHub (May 7, 2015):
i have downloaded the latest release and testing it
@yankejustin commented on GitHub (May 7, 2015):
Seems good. Unless otherwise stated by @DragonzMaster if a problem is seen again, this can probably be closed.
@DragonzMaster commented on GitHub (May 7, 2015):
no no i haven't seen the problem again since using the latest commit until now
good work guys 👍