Fixing Ubuntu theme Gnome Shell 3.6 metacity theme Bug (workaround)

Many thanx to reference source you made my day.

    I just realize that the metacity theme (window decorator) from Gnome Cupertino did not applied when I use it, even though the theme maker already include metacity theme in his release.
    This is because Gnome Shell 3.6 Bugs or they're changed without notice. The .themes folder that placed under user's home will not read by the system, so it will not change your window decorator theme.

   Solution 1: we need to move those package to the system wide's themes folder; /usr/share/themes/
 i.e.: /usr/share/themes/GnomeCupertino 

   Solution 2: make a themes folder under ~/.local/share/ then move that theme into this folder
i.e.: ~/.local/share/themes/GnomeCupertino 
Note: With this solution the themes in this folder will not appear in the Gnome tweak tools.

   Solution 3: make a symbolic link from ~/.themes to the ~/.local/share/
$ln -s ~/.themes ~/.local/share/themes

• Use the Gnome Tweak tools to select the theme you want 
• Alt+F2 put r then Enter to refresh the changed.

PS: Use Gnome Cupertino (gtk theme) with Zukitwo cupertino (gnome shell theme) is ROCK! ;)

Reference: http://www.fandigital.com/2012/10/use-custom-theme-in-gnome-shell-36.html

XFCE settings on Ubuntu 12.10

    Want to try other window manager than Gnome-shell, which gave me some annoying trouble; hang, freeze need to restart lightgdm or force restart the machine. So, here we go.
   Thanks to K.Thep. your post inspired me to choose XFCE4 (http://thep.blogspot.com/2012/11/my-alternative-desktops-3-xfce.html).

   This post kind of memo to my settings ;) 

Theme

1. https://p0ngbr.deviantart.com/art/Fundamental-Round-for-XFCE-197537212
   *This on cannot move window button to the left side
2. https://p0ngbr.deviantart.com/art/Moira-for-XFCE-279849551 
3. http://xfce-look.org/content/show.php/Greybird?content=142534 

Utility

    Keyboard language switching
[ref: http://crunchbang.org/forums/viewtopic.php?id=13026]

    sudo apt-get install xfce4-xkb-plugin

Then we can add it via panel applet.

Fixed : Jenkins SVN plugin always throw No credential to try. Authentication failed

I'm Using Jenkins 1.466.2 with Subversion plugins. Config it to always checkout the source code to build every day. One day it cannot build and show this error in the Source Code Management session.

ERROR: Failed to tag org.tmatesoft.svn.core.SVNCancelException: svn: No credential to try. Authentication failed

No matter how I try to enter the correct credential, by click the follow suggest link "Maybe you need to enter credential?" 

 Solution: 

    Got a clue from these post 

1. http://stackoverflow.com/a/4652362.
2. http://blog.vinodsingh.com/2009/08/hudson-svn-authentication-cancelled.html 

    I dig in to my .subversion folder; it's in your home directory. 
1.
This is my ~/.subversion/servers file; the configuration that different than the default one is this line.

...
store-plaintext-passwords = yes

...

2.

I found a file 550564593bc22e0166f1d522f51755cc under ~/.subversion/auth/svn.simple/
   I look into its content
$cat ~/.subversion/auth/svn.simple/550564593bc22e0166f1d522f51755cc
K 15
svn:realmstring
V 103
<http://filexchange.{cannot exposed}.com:80> {cannot exposed} System 2.0 Repository Login
K 8
username
V 6
dahoba
END

There's password missing?, I thought. So, I try remove the file 550564593bc22e0166f1d522f51755cc and then try to checkout by command line again

$svn --username dahoba co http://filexchange.cannot-exposed.com/svn/2.0/main/program/trunk/app.web .

It will ask for password again, input the correct password and I choose to kept plain password. If we check the content of a file again, the file 550564593bc22e0166f1d522f51755cc was re-generated.

$cat ~/.subversion/auth/svn.simple/550564593bc22e0166f1d522f51755cc

K 8

passtype

V 6

simple

K 8

password

V 9

rm$pdc124

K 15

svn:realmstring

V 103

<http://filexchange.{cannot exposed}.com:80> {cannot exposed} System 2.0 Repository Login

K 8

username

V 6

dahoba

END

    Now, back to Jenkins web console, navigate to jobs configuration, the problem should now gone.

PS: Jenkins deployed on a Ubuntu server
PS: username, servername, repository name was changed, I cannot expose those information to public.