Starting Chrome in Windows 7 guest from Virtualbox happens to see only flicking windows with flashing rate around 2-4 rounds per sec.

Solution:

Turn off hardware acceleration in Chrome setting or uncheck 3D acceleration in Virtualbox.

Tricks:

When flicking occurs, you cannot start Chrome, thus no way to turn off hardware acceleration at setting. Either start Windows in safe mode, then start Chrome and change setting or shutdown windows then uncheck 3D acceleration setting in Virtualbox, and start windows again.

Config:

• Chrome 47.0.2526.80 m (64-bit) for Windows
• Windows 7 Service Pack 1
• Virtualbox  5.0.10

The post Google Chrome Not Start Only Flicking appeared first on LarryLai.

Firefox has been widely deployed in various Linux distributions and Mac OS X. Recently, it has been the default browser for most Linux distributions. Most of the web-based applications claimed to be well tested in Firefox. Thus, it is supposed that firefox is a standard browser. However, it may sometimes go wrong for accessing several webpages with bad behaviours after working healthily for a period of time.

Issue:

If some of the bad behaviours happen in Firefox like the case that the display refreshes so slow or even stalled such that some of the fonts or images either disappear or displayed stranagely.

If you are desparate with the situation that there is no solution on this issue on the web or even no similar issue posted, or already tried something like running Firefox in “safe mode” to troubleshoot the problem. Then the following may be a cure to the problem described below.

Solution:

1. In case you find that your firefox works properly by other users in your machine. In case only one non-root user is created, then it is not bad to try using root user to check the firefox behaviour. If it works properly under other users, then the issue may be all about bad user profile of firefox. You can copy and replace the firefox user profile of bad behaviour by that of the good behaviour using root access.
2. The profile directory is located in ~/.mozilla/firefox/
3. Either change the profile directory name after copying or just modify the content of the profile.ini file.
4. If you are heavily using firefox as default browser, in the long-term, I suggest that you back up your firefox user profile of the good behaviour.

Trick:

1. If you have not installed any Add-ons or extension to your firefox, then probably restarting in “safe mode” does not help.
2. If guessing the Firefox goes too slow to trigger the bad behaviours and suggested by disabling “hardware acceleration“, in this case, this action does not help.
3. Re-installing firefox will not remove the bad firefox user profile residing in “/home/[user]/.mozilla/firefox” directory. It must be removed or replaced by a good profile manually. Though my case happened in openSUSE, I am quite sure it will happen in other Linux distributions, and the cure is similar to the above.

Config:

• openSUSE 12.3
• Firefox 19.0.2 (openSUSE branded)

The post Firefox Bad Behaviour in Linux appeared first on LarryLai.

Some Web Applications provide feature to force direct to https from http links either at installation stage or configured later by application administrators, but some web applications do not provide such security feature.

Solution:

a general workaround is to create a .htaccess file in the root directory of the web application. .htaccess should including the following lines:

• RewriteEngine On
• RewriteCond %{HTTPS} off
• RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
• Only set up the above usually doesn’t work because there is restriction in the config. file of Apache for such change in the web application access.

The following error message will appear in error_log of httpd:

RewriteEngine not allowed here

Tricks:

Directive such as follows should be added to httpd.conf:

• AllowOverride AuthConfig Limit FileInfo Options
• Order allow,deny
• Allow from all

Configuration:

• Apache/2.2.2 (Fedora 5)
• mod_ssl/2.2.2
• OpenSSL/0.9.8a
• TLSv1

The post Apache Config – Force https appeared first on LarryLai.

the Squirrelmail client works fine w/o setting anything. Thunderbird mail client could not access the SMTP server.

Then executive the following:

amend tcp.smtp to add the WAN address of the gateway

cd /etc; tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp

reload smtp cdb by executing ‘qmailctl cdb’

Thunderbird mail client worked properly.

See Qmail Setting Up Servers.

The post SMTP server Config. Verification appeared first on LarryLai.