I have a Samsung Galaxy Chromebook. My cursor keeps being stuck in one place and sometimes it just starts clicking I know that because everything keeps getting selected like when you double or triple-click.
I searched on google first and it said you can reset(didn't help), press escape multiple times, turn off and on (when I do this it stops being stuck for a movement but then it happens again after some time.), drumroll your fingers, and see if there is dust(i cleaned it thoroughly).
Nothing gave a permanent solution. I am a student and I can't just turn it off and on in the middle of online classes.
PLEASE HELP ME
there are many reasons a mousepad can start acting weird. I have one suggestion that might work as this has fixed it for me before.
If you open the computer, most likely there will be some simple connections for the keyboard, storage etc under the battery. Try disconnecting and reconnecting the blue mousepad connection tab. If you have trouble opening the computer, there are plenty of quick tutorials out there. https://www.youtube.com/watch?v=v1JWSnk6uZY.
Related
There are actually two camera problems.
The first is that sometimes the RMB to control the camera angle in Studio doesn't work. Sometimes using the LMB or movement keys helps, other times (like right now) it doesn't do anything. The hand cursor appears to shake in the direction I want to pan the camera but nothing happens. I did have an Advanced Camera plugin.
When I'm testing my game in Studio, I have NO camera control via RMB and zooming is nonfunctional. This is to say that I can turn using my mouse, but RMB doesn't change how mouseview works. Probably unrelated, but I cannot get scripts from the toolbox for run, crouch, zoom, etc. to work, either, even when I place them where instructed.
I get these errors in my game:
16:36:47.313 ▼ ActivateCameraController did not select a module. (x3) - Client - CameraModule:362
16:36:47.314 ActivateCameraController did not select a module.
16:36:47.314 ActivateCameraController did not select a module.
I've been having trouble with Studio eating up too much bandwidth when NOT in use during actual gameplay in Roblox (exe), so I removed all the Studio plugins, thinking one of them might be the culprit (deliberate or accidental), and also hoping it might fix the camera issues. No such luck.
Probably unrelated, but I found a couple of apparently simple viruses (Vaccine and Fire) using clone() and spread() to reproduce within the confines that their simple scripts dictated. I removed all instances, as well as a presumably fake Antivirus. The first two were very basic scripts designed to spread the script and didn't do any damage (although the latter would damage players).
#Kylaaa came up with the answers, but there's no way for me to mark them as answers.
The problems did not occur in a new game until I copied all the stuff I'd added into it (from the troubled game).
Regarding RMB not working in the Studio:
Sometimes, if the Workspace Camera gets set to Scriptable, all mouse inputs stop working. You could try checking if switching the CameraType to Fixed or anything else fixes your problem. It should be in the Properties window when you select the Camera in the Workspace.
What I did: I changed the mode and the problem stopped. I suspect that the Advanced Camera plug-in that I had removed had something to do with the problem.
Regarding the camera not zooming and RMB not working during testing:
you have a malicious script somewhere in your Workspace. You can search/filter the workspace for Script and it will show all of the objects with scripts in them. I would recommend removing or Disabling the each of the scripts until you find which one is causing the errors
When you click on a Script in the Explorer, look in the Properties widget. There should be a checkbox titled Disabled. When you select that, it will prevent the script from running when the game starts
What I did: I deleted a bunch of stuff my son had added, and then disabled ALL scripts, then started enabling them one unique instance at a time (i.e. duplicates were enabled simultaneously). The camera problem didn't come back except when I edited a script during testing. I never located the problem script, despite going through and triggering all scripts.
As the title suggests, my touchpad won't move my mouse. I am therefore unable to select outputs of my commands, but I am able to take screenshots of windows. (Luckily I am used to using keyboard shortcuts)
I have no clue what caused this. I have recently updated my kernel from linux52 to linux53 and linux54. Falling back to either of those versions from linux54 hasn't helped. I have also recently been playing around with a Wacom tablet, using xsetwacom, but I believe my mouse has worked after this.
I know it's not a hardware issue, as libinput debug-events correctly detects my finger running over the trackpad:
The output of 40-libinput.conf in /usr/share/X11/xorg.conf.d/40-libinput.conf is the following. I can't see any error there.
I tried blacklisting the i2c_hid, as suggested in the following question, but to no avail. It fixed an error claiming there was a duplicate mouse, which it decided to ignore. I thought this would help.
What is surprising is that I can click. I can't scroll or move the mouse, though. My trackpad lists the following settings. To my surprise, there is no Accel Speed there, and I can't manually set it with xinput --set-prop 14 'libinput Accel Speed' 1.0, as I need to specify the type and format. I don't know what these are supposed to be, and I don't know if the acceleration is the issue. I read that having a negative value would cause the mouse to never move, though.
Do you have any suggestions as to what to do? What does libinput do with the events after receiving them?
EDIT: Removing the blacklist i2c_hid from the modprobe returns the following Xorg log:
Making a copy of /usr/share/X11/xorg.conf.d/70-synaptics.conf into my /etc/X11/xorg.conf.d/ folder, and commenting out the Option "Ignore" "on" line fixed it.
Had to sudo pkill X after changing it, of course. A reboot would also do the trick.
My 2 weeks old computer doesn't power up anymore! After unplugging it from USB-C docking station I'm not able to get it working again - no sound, picture, connection.
Here is what I've tried:
hold the power button for ~10s, then pressing it again
hold Option+Cmd+Shift+Alt and press power for ~10s
hit the computer hard (this is how I usually repair stuff)
verify that the power adapter is working correctly
call support
Nothing helped :(
After giving up and having a beer I decided to give it last try.
I've opened the lid and started pressing the power button like crazy (~6Hz = ~6 times a sec).
After 5s I've noticed the backlight to turn on and after few seconds the sleeping beauty woke up like nothing ever happened! Since then, everything is fine..
I'm happy, but scared at the same time as
I don't know what caused this issue
how I fixed it
why holding the power button for ~10s didn't have any effect
X-Post from here, for exposure: https://community.onsen.io/topic/222/monaca-ide-console-log-never-appears
Odd question, but only once while using Monaca IDE has anything ever shown up in the console.log portion of the IDE itself. It only occurred when I had a device synced via the debugger. I have since tried syncing it and I never get the device to show in the drop down box, it usually says unknown device /www/html/…
Now, do know that I have put several console.log(‘test’); lines of code to try this out and still no success. I would think that the IDE’s console area would show the log operations from the emulator and not from the device debugger as it has its own log that is view-able on the device, but this apparently isn’t the case. Is this correct or am I just really missing something simple here?
So this isn’t that big of an issue, but I figured out the problem. Basically, I keep the Monaca IDE tab open in Chrome all the time (I work via my laptop remotely). When I come back after a long absence (several hours, I don’t know what the time out is), the bottom section in the console has the Chrome error showing, like that page timed out. The IDE is still there, just that section is grayed out.
So to fix this, I would just refresh the page. The section pops back and all is good EXCEPT I just figured out that it is at that moment when the device connection no longer works. I can still click Run on Device and it works - syncing with the device - but the console.log no longer shows up. In order to get that back and working, you have to close the tab and reopen it; then everything works.
I can't get WinPhone 7 SDK update v7.1.1 to install. It freezes my computer everytime I try to install, the mouse still work but after a while whole system locked up and I need to hold power button to turn it off. Looked at task manager and look like it freeze when configure the emulator. Tried several time, even reinstall Windows and still no luck. Anyone know a work around on this? I saw some others faced this problem but no solution.
When it freezes (in particular, when the spinning icon freezes), try hitting Ctrl+Alt+Del once. Two things can happen:
The first is that the machine will completely freeze within a minute or two, which will require a hard reboot.
The second is that the screen will flicker quickly, attempting to show the "Lock/Switch user/Sign out/Change password/Task manager" screen, and then will jump back to the setup screen. You'll then see the progress icon start spinning again, but it will hesitate several more times. It will either freeze the machine again (and if so, do a hard reboot and try again), or setup will eventually complete (which on my machine took no longer than 10 minutes).