Re: How To Enable Ctrl C And Ctrl V On Chromebook
Argimiro Krishnamoorthy
I'm a normal-sighted person and I would like to view pages at 100% all the time. I use keyboard shortcuts that involve Ctrl a lot, so about twenty times a day I accidentally hit Ctrl at the same time that I'm scrolling, which results in the page being reflowed and repainted. This is annoying because it can take up to 30 seconds to fix the issue, depending on how complex the site layout is. On sites with dynamic layout such as Google Docs the problem is more serious; accidentally hitting Ctrl+mouse wheel corrupts the display and forces me to refresh the page entirely, sometimes causing me to loose information in the process.
I would like to either decouple Ctrl+mouse wheel from zoom, or disable zoom functionality altogether. This is possible on Firefox by using about:config; is there a similar way to edit detailed settings in Chrome? Would I have access to the detailed settings if I used Chromium instead of Chrome? I'll probably jump ship back to Firefox if I can't solve this problem.
There is a superuser question that asks basically the same thing I'm asking, but for Firefox and Internet Explorer exclusively. Other people on the Chrome forum have had related issues, but none have the same problem. "I would really like it if I could deactivate the auto zoom in/out." had "something with laptops and Windows 7", not the feature built into Chrome. Other people have had PDF specific issues, which doesn't concern me.
I've also tried searching for extensions that allow you to disable the scroll; I had hoped that "Zoom Lock" would have the ability to lock the zoom at 100% and prevent Ctrl+scroll wheel from distorting the display, but it doesn't work for my use case.
It doesn't look like its possible within chrome at this point, but you could do it from the mouse side. Depending on the drivers for your mouse, you could set ctrl-scroll as a "shortcut" to actually do nothing - essentially capturing the combination and throwing it away. Some drivers will even let you specify this for only within a certain application, at which point you'd specify chrome.
I have been having an almost identical problem. I'm viewing chrome from a laptop with a built in mouse and no actual wheel, but I would touch the mouse a certain way and find it inexplicably zooming in and out of a page. I am not at all what one would call computer savvy but after reading the first answer I started poking around in my device settings. I found the driver for the mouse, poked around a bit more and eventually found an option to disable "pinch zoom", which thus far seems to have fixed the problem.
I made the transition from Windows 7 to Mint a year or so ago and had the same problem. Now I find myself using a combination of tools to approximate my rather hefty collection of AHK macros and AHK in a virtualbox Windows VM when I can't get around using MS apps or Windows utilities.
For more complicated stuff like changing window geometries and so forth, in Mint 17 I mostly use the wmctrl utility. In Min 16, a great little utility called devilspie with a gdevilspie GUI would automatically change the position and geometry of any window I specified, on opening. Unfortunately, devilspie doesn't work in Mint 17. I keep hoping it'll get fixed in Mint 17 and wishing I knew how to fix it myself.
Incidentally, the problem with wine and AHK is, wine can't access lower-level functions, so you can't use ahk's keyboard or mouse hooks. But I've got to the point where I don't much miss AHK; I simply do the same things with bash aliases or scripts. It's not very hard to kluge together macros using combinations of :
Oddly, now that I'm used to the approach it seems no harder to use than AHK was. But then I've just gotten to where playing with Linux is as much fun as DOS was back in the days of the dinosaurs. I'd missed that with later stay-inside-the-lines Windows versions.
If you do not need Ctrl clicking, you could solve the problem by disabling mouse completely during such a modifier key is down. My answer should work in Unix-like operating systems that use X. This effect is by no means restricted to Chrome.
You need to modify the script below to match your keyboard and pointer hardware. See the comments (i.e. lines that start by #) for more information. After you have modified the script, just save it in a file, make it executable by chmod +x and run it at startup.
Try making a Ubuntu USB stick with another PC and make it bootable with something like Rufus. After that, plug it in to the Asus and shut the chrome book down. Now, press POWER and start pressing F12 right away.
First of all, it's not a good idea to use the school computer, but you're looking for a way to unlock it, not the answer, right? Let me tell you. This is a fairly easy method, so you can do it in no time. First, press the three dots on the top left. Then, press "More Tools" and press "Task Manager" from among them, and an extended function will appear in the middle of the screen. After pressing "End Process" below, you are now free.
First, sign out of your chromebook. Then, Press Ctrl + Alt + Shift + R At the same time then press Powerwash>Restart Then press the blue button, Then connect to a network and decline all privacy policy.
to remove GoGuardian sign out of your account press ctrl, alt, shift, and r at the same time press restart, and then press powerwash and follow the instructions or you could open the back of computer.
May be late, but a kid at my school found a way a while back. In case all other methods fail, you can buy a new motherboard and replace it through the back. Make sure to get the right model. In case you have to return your Chromebook around the end of the school year (if you don't own it). When times come, switch out the motherboards again and pretend like nothing ever happened. It worked for him multiple times and it will most likely work for you too. May be pricey, but there will be little to no permanent damage.
@haisy The model number will be printed on a label on the bottom of the computer. If we're still talking about this particular Chromebook, then you can see the label on the first step of the palm rest replacement guide here.
In most cases this will be all you need, but if you open it up and check the motherboard, there may be a separate model number just for the motherboard; if that's the case it would be best to use the motherboard number since that will always give you an exact match.
This article was created to provide information on how to get Arch installed on the series of Chrome OS devices built by Acer, HP, Samsung, Toshiba, and Google. Currently this page is being overhauled, and more model specific pages are being built with some of the information listed below.
All recent Intel-based Chrome OS devices (starting with the 2013 Chromebook Pixel) feature a Legacy Boot Mode, designed to allow the user to boot Linux. Legacy Boot Mode has a dedicated firmware region, RW_LEGACY, which is designed to be user-writeable (hence the 'RW' notation) and is completely separate from the ChromeOS portion of the firmware (ie, it is safe to update and cannot brick the device). It is enabled by the SeaBIOS payload of coreboot, the open-source firmware used for all Chrome OS devices (with the exception of the first generation of Chromebooks and a few early ARM models). SeaBIOS behaves like a traditional BIOS that boots into the MBR of the disk, and from there into standard boot loaders like Syslinux and GRUB.
Models with a Core-i based SoC (Haswell, Broadwell, Skylake, KabyLake) mostly ship with a functional Legacy Boot Mode payload; updating to a 3rd party build can provide bug fixes and additional features. Models with an Atom-based SoC (Baytrail, Braswell, Apollolake) have Legacy Boot Mode capability, but do not ship with a RW_LEGACY/SeaBIOS payload (that part of the firmware is blank). These models require a 3rd party RW_LEGACY firmware to be loaded for Legacy Boot Mode to be functional.
All Chrome OS devices features firmware write protection, which restricts write access to certain regions of the flash chip. It is important to be aware of it as one might need to disable the hardware write protection as part of the installation process (to update GBB flags or flash a custom firmware).
To boot SeaBIOS by default, you will need to run the set_gbb_flags.sh script, which is part of ChromeOS. The script uses flashrom and gbb_utility to read the RO_GBB firmware region, modify the flags, and write it back to flash. The GBB flags can also be set using MrChromebox's Firmware Utility Script under either ChromeOS or Arch (the latter requiring booting with specific kernel parameters to relax memory access restrictions).
Your ChromeOS device now will boot to SeaBIOS by default, you can continue to Installing Arch Linux, if your device is booting correctly then you can optionally re-enable the hardware write protection.
If your devices requires a patched kernel, it is advised to review the list of patches and decide if the patch list is getting decidedly small enough that you no longer require a patched kernel and instead you can use the official linux package instead.
xf86-input-cmtAUR offers a port of the Chromium OS input driver: xf86-input-cmt as an alternative for the Synaptics input driver. It provides tweaked configuration files for most devices, and provides functionality that the Synaptics input driver does not such as palm rejection. Additionally, it enables functionality not enabled by default in the Chromium OS input driver such as tap-to-drag.
Please note, the input driver does not work under some circumstances where you have insufficient permissions to access /dev/input/eventThis will affect you if you use startx to load a DE/WM session.If this is the case or if the driver does not load for any other cases, you should run:
The following are instructions to fix the suspend functionality.Users of a pre-installed SeaBIOS or John Lewis' pre-built SeaBIOS you will need this fix.This procedure is not needed with Matt DeVillier's custom firmware since problematic ACPI wake devices (such as TPAD) are firmware-disabled.
d3342ee215