Dig in google-chrome #1

I tried to find why I can't type in input-textbox on some website (known later that has flash 11.3 included). Not sure but the problem gone immediately after I disable flash (some pepper version). So I decide to use flash 11.2r202 from adobe website. In tar.gz type, I discovered that google-chrome not just store files in ~/.config/google-chrome but in /opt/google/chrome as well. Seem like this is the truth solution but not event close, because my chrome does not seem to feel a new plugin (libflashplayer.so). So I try to put it in /usr/lib/mozilla/plugins. From doing this, it's work. That's it.

** Download
install_flash_player_11_linux.x86_64.tar.gz from adobe web. After untar we'll get
- libflashplayer.sh
- readme.txt
- usr folder

**** you should follow the instruction in readme.txt

Comments

Post a Comment

Popular posts from this blog

Return Code 127

Exit codes and kill-job signals The exit code from a batch job is a standard Unix termination status, the same sort of number you get in a shell script from checking the " $? " variable after executing a command. Typically, exit code 0 (zero) means successful completion. Codes 1-127 are typically generated by your job itself calling  exit()  with a non-zero value to terminate itself and indicate an error. In BaBar we don't make very much use of this. The most common such value you might see is 64, which is the value used by Framework to say that its event loop is being stopped before all the requested data have been read, typically because time ran out. In recent BaBar releases you might also see 125, which we use as a code for a generic "severe error"; the job log should contain a message stating what the error was. Exit codes in the range 129-255 represent jobs terminated by Unix " signals ". Each type of signal has a number, and what's r
Read more