Sunday, August 31, 2014

[Alt] key problem when remote desktop Windows via Remmina

If you are using Xfce 4 and encounter the following problems using [Alt] key inside Microsoft Windows remote desktop session:

  • [Alt] key does not work as per expected
  • clicking [Alt] + mouse middle button move you away from your remote desktop session
then you should try this simple and straight forward trick before going too technical.
  • Go Settings > Settings Manager > Window Manager Tweaks > Accessibility > "Key used to grab and move windows" > set it to "None"

Voila! Now it should works like charm. Otherwise... you might have to Google around and read about re-map key, etc.. Good luck!

Tuesday, August 19, 2014

Remmina - Unable to connect RDP Server

Have you ever encountered sudden failure to RDP to your Windows desktop using Remmina? There are two known reasons to me:

  1. your RDP plugin for Reminna is missing. In Fedora, type sudo yum install remmina-plugins-rdp, or Ubuntu sudo apt-get install remmina-plugin-rdp. You may require to reboot after install in order to load the RDP plugin. Sometimes Import simply won't work.
  2. your remote desktop's fingerprint has changed. It is impossible to reset the fingerprint within Remmina's interface. What you can do is fire up terminal, go to ~/.freerdp/ and delete known_hosts.
Now try again and voila! Your remote desktop is back!

Saturday, June 21, 2014

[Fedora] Omit GUI and boot with or into command line

Before you start, you need to know what is runlevel.
runlevel is a number that indicates which mode the computer to boot into. For instance, runlevel 5 is graphical mode, where runlevel 3 is text-only mode. Runlevel 1 is single-user mode, commonly used for troubleshooting.
And GRUB (GRand Unified Bootloader), a bootloader which allow you to choose which OS to boot into during computer start up. Here's a screenshot of GRUB.

Now, there are two options:
  1. boot with command line, means omit the filling up Fedora logo and show the boot progress by command line
  2. boot into command line, means completely omit booting into GUI and end up in command line
What you need to do is at the GRUB screen, select your Fedora OS name and press "e".
Then find rhgb in the line start with linuxefi /vmlinuz. On the right side of rhgb should be word "quiet".

For option 1: Remove the rhgb from the line and press CTRL+X or F10. This should show the command lines as boot progress instead of the Fedora logo. Useful for identifying what has failed during boot progress. The system will still end up in GUI afterwards.
Sample = ... rhgb quiet ... 

For option 2: Here's why you have to understand the runlevel. You achieve this by simply add a runlevel number "3" after the word "quiet" (space in between two words) and press CTRL+X or F10. This should boot the system into CLI instead of GUI.
 Sample = ... rhgb quiet 3 ...

  • rhgb = RedHat Graphical Boot

Thursday, April 10, 2014

Enable Samba browsing in Thunar

If you enter location path start with smb:// and get a red stop sign, it means you don't have gvfs-smb install. Simply fire up your terminal and type:
sudo yum install gvfs-smb -y
You might want to install Gigolo too to manage your network folder.
sudo yum install gigolo -y
 Voila! Your address bar should work with smb:// now.

Thursday, January 16, 2014

Problem connecting Xrdp

If the error appeared as "problem connecting" when connecting to remote desktop using xrdp, it is most likely the remote Linux does not have VNC server installed.

(1) To verify this, you can type:
sudo tail /var/log/xrdp-sesman.log

(2) If you see the error message below, then it means you don't have VNC server installed.
[ERROR] another Xserver is already active on display xx 

(3) To fix this, simply run this command:
sudo apt-get install tightvncserver

(4) After that, restart xrdp service by running:
sudo service xrdp restart

Here's why:
xrdp is the daemon that handles RDP remote desktop access from Windows machines to your Linux Mint PC. But it's not enough to install only xrdp - you need a VNC server. Unfortunately it's not automatically installed with the xrdp package.

The error message "error - problem connecting" after a successful login message isn't very helpful either. Searching the Internet can drive you in circles - I wasted at least 2 hours on finding out that I forgot to install the VNC server - ouch.

Thanks powerhouse from Linux Mint forum who shared this useful information.

Thursday, December 5, 2013

Samba Share Permission in a Nutshell

In this post I'm writing all the troubles that I faced when setting up samba shares for Windows and MAC, to help novice users get the samba up and running as quickly as possible. Do note that all the tips & tricks shared here is meant to get things up and running quickly, it might create security hole. Use at your own risk and be sure to research more if you are deploying for high security concern mission.

New created folder or copy & paste into samba shared folder do not follow permission set by smb.conf
The key settings are the following (e.g. permissions 775)
  • create mask = 0775
  • force create mode = 0775
  • security mask = 0775
  • force security mode = 0775
  • directory mask = 2775
  • force directory mode = 2775 (If you change this to 0755, it won't work. So this parameter is very important)
  • directory security mask = 2775
  • force directory security mode = 2775
Now, why 2775?
  • 2 = the setgid bit is set (2) which makes newly created directories have the same group ownership as the parent.
  • 77 = owners and group members of the files have full access to them
  • 5 = everyone else can enter the directories and view the file names (use with caution)
To be continue...

Saturday, October 12, 2013

Terminal does not have history and not showing path?

What happen when a new user's terminal (xterm, lxterminal etc):

  1. does not display any path (only show $>)
  2. does not support Up key for recall previous command?
It is because the new user is using /bin/sh instead of /bin/bash. To solve this, simply do sudo chsh, then key in /bin/bash when prompted to choose an option.

Restart the terminal then you should be able to get all the features back.

The root cause for this is nothing is specified when the user is being created using command line. Be sure to specify to use /bin/bash to avoid this.