Difference between pages "Keychain" and "Package:Xfce4-settings"

(Difference between pages)
m (Undo revision 8666 by Aphyr (talk))
 
(Added information about configuring the Desktop)
 
Line 1: Line 1:
{{Article
+
{{Ebuild
|Subtitle=Official Project Page
+
|Summary=The configuration system for XFCE
|Summary=Keychain helps you to manage SSH and GPG keys in a convenient and secure manner. Download and learn how to use Keychain on your Linux, Unix or MacOS system.
+
|CatPkg=xfce-base/xfce4-settings
|Keywords=keychain,ssh,rsa,dsa,gpg,linux,gentoo,macos,download,source code
+
|Homepage=http://docs.xfce.org/xfce/xfce4-settings/start
|Author=Drobbins
+
 
}}
 
}}
<tt>Keychain</tt> helps you to manage SSH and GPG keys in a convenient and secure manner. It acts as a frontend to <tt>ssh-agent</tt> and <tt>ssh-add</tt>, but allows you to easily have one long running <tt>ssh-agent</tt> process per system, rather than the norm of one <tt>ssh-agent</tt> per login session.
+
{{c|xfce4-settings}} provides two main utilities used to configure key components of the XFCE desktop environment:
 +
* {{c|xfce4-settings-editor}}: Provides a {{c|dconf-editor}}-like interface used to configure components of XFCE ranging from Thunar to the XFCE notification daemon.
 +
* {{c|xfce4-settings-manager}}: Allows users to configure the same components as can be configured in the {{c|xfce4-settings-editor}} but provides a more easy to understand interface for configuration.
  
This dramatically reduces the number of times you need to enter your passphrase. With <tt>keychain</tt>, you only need to enter a passphrase once every time your local machine is rebooted. <tt>Keychain</tt> also makes it easy for remote cron jobs to securely "hook in" to a long-running <tt>ssh-agent</tt> process, allowing your scripts to take advantage of key-based logins.
+
== Installation ==
 
+
If you have already installed the XFCE desktop environment using the {{c|xfce4-meta}} package, {{c|xfce4-settings}} should be installed. Also, if you have installed an XFCE program such as thunar in another desktop environment or window manager such as Openbox or KDE, {{c|xfce4-settings}} is probably installed on your system too. If, for some reason, the program is not installed in either of those cases and you wish to emerge it, run the command:
Those who are new to OpenSSH and the use of public/private keys for authentication may want to check out the following articles by Daniel Robbins, which will provide a gentle introduction to the concepts used by Keychain:
+
{{console|body=
* [[OpenSSH Key Management, Part 1]]
+
###i## emerge xfce4-settings
* [[OpenSSH Key Management, Part 2]]
+
* [[OpenSSH Key Management, Part 3]]
+
 
+
== Download and Resources ==
+
 
+
The latest release of keychain is version <tt>2.7.2_beta1</tt>, and was released on July 7, 2014. The current version of keychain supports <tt>gpg-agent</tt> as well as <tt>ssh-agent</tt>.
+
 
+
Keychain is compatible with many operating systems, including <tt>AIX</tt>, <tt>*BSD</tt>, <tt>Cygwin</tt>, <tt>MacOS X</tt>, <tt>Linux</tt>, <tt>HP/UX</tt>, <tt>Tru64 UNIX</tt>, <tt>IRIX</tt>, <tt>Solaris</tt> and <tt>GNU Hurd</tt>.
+
 
+
=== Download ===
+
 
+
* ''Release Archive''
+
** [http://www.funtoo.org/distfiles/keychain/keychain-2.7.2_beta1.tar.bz2 keychain 2.7.2_beta1]
+
** [http://www.funtoo.org/distfiles/keychain/keychain-2.7.1.tar.bz2 keychain 2.7.1]
+
 
+
* ''Apple MacOS X Packages''
+
** [http://www.funtoo.org/distfiles/keychain/keychain-2.7.1-macosx.tar.gz keychain 2.7.1 MacOS X package]
+
 
+
Keychain development sources can be found in the [http://www.github.com/funtoo/keychain keychain git repository]. Please use the [https://bugs.funtoo.org Funtoo Linux bug tracker] and [irc://irc.freenode.net/funtoo #funtoo irc channel] for keychain support questions as well as bug reports.
+
 
+
=== Project History ===
+
 
+
Daniel Robbins originally wrote <tt>keychain</tt> 1.0 through 2.0.3. 1.0 was written around June 2001, and 2.0.3 was released in late August, 2002.
+
 
+
After 2.0.3, <tt>keychain</tt> was maintained by various Gentoo developers, including Seth Chandler, Mike Frysinger and Robin H. Johnson, through July 3, 2003.
+
 
+
On April 21, 2004, Aron Griffis committed a major rewrite of <tt>keychain</tt> which was released as 2.2.0. Aron continued to actively maintain and improve <tt>keychain</tt> through October 2006 and the <tt>keychain</tt> 2.6.8 release. He also made a few commits after that date, up through mid-July, 2007. At this point, <tt>keychain</tt> had reached a point of maturity.
+
 
+
In mid-July, 2009, Daniel Robbins migrated Aron's mercurial repository to git and set up a new project page on funtoo.org, and made a few bug fix commits to the git repo that had been collecting in [http://bugs.gentoo.org bugs.gentoo.org]. Daniel continues to maintain <tt>keychain</tt> and supporting documentation on funtoo.org, and plans to make regular maintenance releases of <tt>keychain</tt> as needed.
+
 
+
== Quick Setup ==
+
 
+
=== Linux ===
+
 
+
To install under Gentoo or Funtoo Linux, type
+
<console>
+
###i## emerge keychain
+
</console>
+
 
+
For other Linux distributions, use your distribution's package manager, or download and install using the source tarball above. Then generate RSA/DSA keys if necessary. The quick install docs assume you have a DSA key pair named <tt>id_dsa</tt> and <tt>id_dsa.pub</tt> in your <tt>~/.ssh/</tt> directory. Add the following to your <tt>~/.bash_profile</tt>:
+
 
+
{{file|name=~/.bash_profile|body=
+
eval `keychain --eval --agents ssh id_rsa`
+
 
}}
 
}}
  
If you want to take advantage of GPG functionality, ensure that GNU Privacy Guard is installed and omit the <tt>--agents ssh</tt> option above.
+
After the emerge has finished, you can check that the package was successfully installed by running the command {{c|xfce4-settings-manager}} or by launching the program from your dock. If the package did install, you should be greeted with a window titled "Settings" that is divided into several sections with names like "Personal" and "Hardware." If the program does not launch after repeated attempts, consider filing a bug report at [http://bugs.funtoo.org Funtoo Bugs].
  
=== Apple MacOS X ===
+
== Usage ==
 +
To run {{c|xfce4-settings-manager}} in XFCE, navigate to the applications menu in your panel, go to "Settings" and then select "Settings Manager." Alternately, you can open your terminal emulator and type "xfce4-settings-manager" and press enter to launch the program. In other desktop environments, launch the program as you would any other.
  
To install under MacOS X, install the MacOS X package for keychain. Assuming you have an <tt>id_dsa</tt> and <tt>id_dsa.pub</tt> key pair in your <tt>~/.ssh/</tt> directory, add the following to your <tt>~/.bash_profile</tt>:
+
=== Appearance ({{c|xfce4-appearance-settings}}) ===
 +
==== Style ====
 +
After clicking on the "Appearance" subsection in the section "Personal," you will find yourself in a tab titled "Style." This tab allows you to select the GTK+ theme that you would like to use from a list of themes that are currently installed in either {{c|/usr/share/themes}} or {{c|~/.themes}}. The three colored boxes to the left of the theme name show the theme's colors. To select a GTK+ theme as default, simply click on it and your theme will change immediately.
 +
{{note|If the theme does not change when clicked, double check to see that you are launching XFCE with the {{c|--with-ck-launch parameter}}. Theming using {{c|xfce4-settings-manager}} does not seem to work without it.}}
  
{{file|name=~/.bash_profile|body=
+
==== Icons ====
eval `keychain --eval --agents ssh --inherit any id_dsa`
+
To select the default icon theme for XFCE, click on the tab with the text "Icons." This tab, not surprisingly, allows you to edit your icon theme. To change your icon theme, click on the one that you like and the theme will change immediately. If it does not, read the above note.
}}
+
{{tip|To install new icon themes, extract an icon theme to either {{c|/usr/share/icons}} (for every user on the system) or to {{c|~/.icons}} (for just you).}}
  
{{Fancynote|The <tt>--inherit any</tt> option above causes keychain to inherit any ssh key passphrases stored in your Apple MacOS Keychain. If you would prefer for this to not happen, then this option can be omitted.}}
+
==== Fonts ====
 
+
To change the default font, the DPI value of the current font, or to enable font anti-aliasing, click on the "Fonts" tab. The default font can be changed quite easily by selecting the box under "Default Font." Selecting this box will bring up a list of all the different font families that are currently installed on your system, along with the available styles for each font family. To change your font, choose the appropriate font family, style, and size and the click the button labeled "OK" at the bottom right of the window. Your font should change immediately. If it does not, the above note may help to solve the problem. A nice default font is "Ubuntu Regular 10," provided by the {{c|ubuntu-font-family}} package which can easily be installed using the following command:
== Background ==
+
{{console|body=
 
+
###i## emerge ubuntu-font-family
You're probably familiar with <tt>ssh</tt>, which has become a secure replacement for the venerable <tt>telnet</tt> and <tt>rsh</tt> commands.
+
 
+
Typically, when one uses <tt>ssh</tt> to connect to a remote system, one supplies a secret passphrase to <tt>ssh</tt>, which is then passed in encrypted form over the network to the remote server. This passphrase is used by the remote <tt>sshd</tt> server to determine if you should be granted access to the system.
+
 
+
However, OpenSSH and nearly all other SSH clients and servers have the ability to perform another type of authentication, called asymmetric public key authentication, using the RSA or DSA authentication algorithms. They are very useful, but can also be complicated to use. <tt>keychain</tt> has been designed to make it easy to take advantage of the benefits of RSA and DSA authentication.
+
 
+
== Generating a Key Pair ==
+
 
+
To use RSA and DSA authentication, first you use a program called <tt>ssh-keygen</tt> (included with OpenSSH) to generate a ''key pair'' -- two small files. One of the files is the ''public key''. The other small file contains the ''private key''. <tt>ssh-keygen</tt> will ask you for a passphrase, and this passphrase will be used to encrypt your private key. You will need to supply this passphrase to use your private key. If you wanted to generate a DSA key pair, you would do this:
+
 
+
<console># ##i##ssh-keygen -t dsa
+
Generating public/private dsa key pair.</console>
+
You would then be prompted for a location to store your key pair. If you do not have one currently stored in <tt>~/.ssh</tt>, it is fine to accept the default location:
+
 
+
<console>Enter file in which to save the key (/root/.ssh/id_dsa): </console>
+
Then, you are prompted for a passphrase. This passphrase is used to encrypt the ''private key'' on disk, so even if it is stolen, it will be difficult for someone else to use it to successfully authenticate as you with any accounts that have been configured to recognize your public key.
+
 
+
Note that conversely, if you '''do not''' provide a passphrase for your private key file, then your private key file '''will not''' be encrypted. This means that if someone steals your private key file, ''they will have the full ability to authenticate with any remote accounts that are set up with your public key.''
+
 
+
Below, I have supplied a passphrase so that my private key file will be encrypted on disk:
+
 
+
<console>Enter passphrase (empty for no passphrase): ##i#########
+
Enter same passphrase again: ##i#########
+
Your identification has been saved in /var/tmp/id_dsa.
+
Your public key has been saved in /var/tmp/id_dsa.pub.
+
The key fingerprint is:
+
5c:13:ff:46:7d:b3:bf:0e:37:1e:5e:8c:7b:a3:88:f4 root@devbox-ve
+
The key's randomart image is:
+
+--[ DSA 1024]----+
+
|          .      |
+
|          o  . |
+
|          o . ..o|
+
|      . . . o  +|
+
|        S    o. |
+
|            . o.|
+
|        .  ..++|
+
|        . o . =o*|
+
|        . E .+*.|
+
+-----------------+</console>
+
 
+
== Setting up Authentication ==
+
 
+
Here's how you use these files to authenticate with a remote server. On the remote server, you would append the contents of your ''public key'' to the <tt>~.ssh/authorized_keys</tt> file, if such a file exists. If it doesn't exist, you can simply create a new <tt>authorized_keys</tt> file in the remote account's <tt>~/.ssh</tt> directory that contains the contents of your local <tt>id_dsa.pub</tt> file.
+
 
+
Then, if you weren't going to use <tt>keychain</tt>, you'd perform the following steps. On your local client, you would start a program called <tt>ssh-agent</tt>, which runs in the background. Then you would use a program called <tt>ssh-add</tt> to tell <tt>ssh-agent</tt> about your secret private key. Then, if you've set up your environment properly, the next time you run <tt>ssh</tt>, it will find <tt>ssh-agent</tt> running, grab the private key that you added to <tt>ssh-agent</tt> using <tt>ssh-add</tt>, and use this key to authenticate with the remote server.
+
 
+
Again, the steps in the previous paragraph is what you'd do if <tt>keychain</tt> wasn't around to help. If you are using <tt>keychain</tt>, and I hope you are, you would simply add the following line to your <tt>~/.bash_profile</tt> or if a regular user to<tt>~/.bashrc</tt> :
+
 
+
{{file|name=~/.bash_profile|body=
+
eval `keychain --eval id_dsa`
+
 
}}
 
}}
 +
If you are unhappy with the scaling of the fonts in XFCE, perhaps because you are using a hiDPI display, consider increasing the value next to "Custom DPI setting." Finally, to make many fonts appear more crisp and well-defined, increase the value in "Hinting" to "Medium" or "Full."
  
The next time you log in or source your <tt>~/.bash_profile</tt> or if you use <tt>~/.bashrc</tt>, <tt>keychain</tt> will start, start <tt>ssh-agent</tt> for you if it has not yet been started, use <tt>ssh-add</tt> to add your <tt>id_dsa</tt> private key file to <tt>ssh-agent</tt>, and set up your shell environment so that <tt>ssh</tt> will be able to find <tt>ssh-agent</tt>. If <tt>ssh-agent</tt> is already running, <tt>keychain</tt> will ensure that your <tt>id_dsa</tt> private key has been added to <tt>ssh-agent</tt> and then set up your environment so that <tt>ssh</tt> can find the already-running <tt>ssh-agent</tt>. It will look something like this:
+
==== Settings ====
 
+
If you do not like having images in menus or buttons or you would like to change the way that toolbars are displayed, navigate to the "Settings" tab. To modify how toolbars appear in GTK+ applications, modify the "Toolbar Style" dropdown to your pleasing. Here is what the different toolbar styles look like:
Note that when <tt>keychain</tt> runs for the first time after your local system has booted, you will be prompted for a passphrase for your private key file if it is encrypted. But here's the nice thing about using <tt>keychain</tt> -- even if you are using an encrypted private key file, you will only need to enter your passphrase when your system first boots (or in the case of a server, when you first log in.) After that, <tt>ssh-agent</tt> is already running and has your decrypted private key cached in memory. So if you open a new shell, you will see something like this:
+
 
+
This means that you can now <tt>ssh</tt> to your heart's content, without supplying a passphrase.
+
 
+
You can also execute batch <tt>cron</tt> jobs and scripts that need to use <tt>ssh</tt> or <tt>scp</tt>, and they can take advantage of passwordless RSA/DSA authentication as well. To do this, you would add the following line to the top of a bash script:
+
 
+
{{file|name=example-script.sh|body=
+
eval `keychain --noask --eval id_dsa` || exit 1
+
}}
+
 
+
The extra <tt>--noask</tt> option tells <tt>keychain</tt> that it should not prompt for a passphrase if one is needed. Since it is not running interactively, it is better for the script to fail if the decrypted private key isn't cached in memory via <tt>ssh-agent</tt>.
+
 
+
== Keychain Options ==
+
 
+
=== Specifying Agents ===
+
 
+
In the images above, you will note that <tt>keychain</tt> starts <tt>ssh-agent</tt>, but also starts <tt>gpg-agent</tt>. Modern versions of <tt>keychain</tt> also support caching decrypted GPG keys via use of <tt>gpg-agent</tt>, and will start <tt>gpg-agent</tt> by default if it is available on your system. To avoid this behavior and only start <tt>ssh-agent</tt>, modify your <tt>~/.bash_profile</tt> as follows:
+
 
+
{{file|name=~/.bash_profile|body=
+
eval `keychain --agents ssh --eval id_dsa` || exit 1
+
}}
+
 
+
The additional <tt>--agents ssh</tt> option tells <tt>keychain</tt> just to manage <tt>ssh-agent</tt>, and ignore <tt>gpg-agent</tt> even if it is available.
+
 
+
=== Clearing Keys ===
+
 
+
Sometimes, it might be necessary to flush all cached keys in memory. To do this, type:
+
 
+
<console># ##i##keychain --clear</console>
+
Any agent(s) will continue to run.
+
 
+
=== Improving Security ===
+
 
+
To improve the security of <tt>keychain</tt>, some people add the <tt>--clear</tt> option to their <tt>~/.bash_profile</tt> <tt>keychain</tt> invocation. The rationale behind this is that any user logging in should be assumed to be an intruder until proven otherwise. This means that you will need to re-enter any passphrases when you log in, but cron jobs will still be able to run when you log out.
+
 
+
=== Stopping Agents ===
+
 
+
If you want to stop all agents, which will also of course cause your keys/identities to be flushed from memory, you can do this as follows:
+
 
+
<console># ##i##keychain -k all</console>
+
If you have other agents running under your user account, you can also tell <tt>keychain</tt> to just stop only the agents that <tt>keychain</tt> started:
+
 
+
<console># ##i##keychain -k mine</console>
+
 
+
=== GPG ===
+
 
+
Keychain can ask you for your GPG passphrase if you provide it the GPG key ID. To find it out:
+
<console>
+
$##i## gpg -k
+
pub  2048R/DEADBEEF 2012-08-16
+
uid                  Name (Comment) <email@host.tld>
+
sub  2048R/86D2FAC6 2012-08-16
+
</console>
+
 
+
Note the '''DEADBEEF''' above is the ID. Then, in your login script, do your usual
+
 
+
<console>
+
$##i## keychain --dir ~/.ssh/.keychain ~/.ssh/id_rsa DEADBEEF
+
$##i## source ~/.ssh/.keychain/$HOST-sh
+
$##i## source ~/.ssh/.keychain/$HOST-sh-gpg
+
</console>
+
  
=== Learning More ===
+
{{TableStart}}
 +
<tr class="info"><th>Style</th><th>Preview</th></tr>
 +
<tr><td>Icons</td><td>[[File:xfce4-settings_toolbar_icons.png]]</td></tr>
 +
<tr><td>Text</td><td>[[File:xfce4-settings_toolbar_text.png]]</td></tr>
 +
<tr><td>Text under icons</td><td>[[File:xfce4-settings_toolbar_text_under_icons.png]]</td></tr>
 +
{{TableEnd}}
 +
To add or remove images on GTK+ buttons, check or uncheck the checkbox adjacent to "Show images on buttons." To remove those ''pesky'' little icons in menus, uncheck "Show images in menus."
  
The instructions above will work on any system that uses <tt>bash</tt> as its default shell, such as most Linux systems and Mac OS X.
+
=== Desktop ({{c|xfdesktop-settings}}) ===
 +
The desktop section of {{c|xfce4-settings}} is, not surprisingly, focused on the customization of the XFCE desktop. It includes options to customize the wallpaper, desktop icons, and desktop menus.
  
To learn more about the many things that <tt>keychain</tt> can do, including alternate shell support, consult the keychain man page, or type <tt>keychain --help | less</tt> for a full list of command options.
+
==== Background ====
 +
The first tab of the desktop section is titled "Background." This tab provides configuration options for the wallpaper of your XFCE desktop. To change the wallpaper for the current desktop, take note of the directory in which you have stored the image that you want to set as your wallpaper {{c|~/Pictures/Wallpapers/}}, for example. Then, click the box next to "Folder" in the bottom of the Background tab. When you click this box, you will get a menu displaying some directories where your photos could be located. If the picture you wish to use is not in any of the listed directories, select "Other..." and a dialog called "select a file will open." Now, navigate to the parent directory of the directory in which your wallpapers are stored ({{c|~/Pictures}} in my case) and click on the icon for that directory (should be called {{c|Wallpapers}} for me). After selecting that directory, click "Open" in the bottom right of the "Select a file" dialog. Now you should be able to choose the wallpaper that you wanted from the "Wallpaper for my desktop" box in the Background tab. To change to that wallpaper, simply click on the image of the desired wallpaper and your background should change immediately.  
  
I also recommend you read my original series of articles about [http://www.openssh.com OpenSSH] that I wrote for IBM developerWorks, called <tt>OpenSSH Key Management</tt>. Please note that <tt>keychain</tt> 1.0 was released along with Part 2 of this article, which was written in 2001. <tt>keychain</tt> has changed quite a bit since then. In other words, read these articles for the conceptual and [http://www.openssh.com OpenSSH] information, but consult the <tt>keychain</tt> man page for command-line options and usage instructions :)
+
==== Menus ====
 +
The "Menus" tab controls the appearance of menus that appear on your desktop when you right and middle click.  
  
* [http://www.ibm.com/developerworks/library/l-keyc.html Common Threads: OpenSSH key management, Part 1] - Understanding RSA/DSA Authentication
+
==== Icons ====
* [http://www.ibm.com/developerworks/library/l-keyc2/ Common Threads: OpenSSH key management, Part 2] - Introducing <tt>ssh-agent</tt> and <tt>keychain</tt>
+
Clicking on the tab labeled "Icons" allows you to customize the appearance of desktop icons. If you do not like having icons on your desktop and have struggled to find a way to remove the "Home," "Filesystem," and "Trash" icons from your desktop, you're in luck! Go to the bottom of the configuration dialog and uncheck all of the boxes in the "Default Icons" box. One by one, those pesky little icons will fade away into the nothingness that they deserve. Conversely, if you love desktop icons, you can always add more by right clicking on your desktop and selecting the appropriate "Create *" option in the menu that appears.
* [http://www.ibm.com/developerworks/library/l-keyc3/ Common Threads: OpenSSH key management, Part 3] - Agent forwarding and <tt>keychain</tt> improvements
+
  
As mentioned at the top of the page, <tt>keychain</tt> development sources can be found in the [http://www.github.com/funtoo/keychain keychain git repository]. Please use the [http://groups.google.com/group/funtoo-dev funtoo-dev mailing list] and [irc://irc.freenode.net/funtoo #funtoo irc channel] for keychain support questions as well as bug reports.
+
To remove the large tooltips that appear when you hover over an icon on your desktop, uncheck the box "Show icon tooltips" in {{c|xfce4-settings}}. You can also shrink the size of the tooltip icon, and hence the tooltip itself, by decreasing the value in the box next to "Size:"
  
[[Category:HOWTO]]
+
{{warning|The rest of this page is still 'under construction.'}}
[[Category:Projects]]
+
=== File Manager ({{c|thunar-settings}}) ===
[[Category:First Steps]]
+
{{EbuildFooter}}
[[Category:Articles]]
+
{{ArticleFooter}}
+

Revision as of 14:07, April 1, 2015

xfce-base/xfce4-settings


Source Repository:Repository:Gentoo Portage Tree

http://docs.xfce.org/xfce/xfce4-settings/start

Summary: The configuration system for XFCE

Use Flags

libinput
Enable libinput Xorg driver (x11-drivers/xf86-input-libinput) support
libcanberra
Enable sound event support using media-libs/libcanberra
xklavier
Enable keyboard layout selection support using x11-libs/libxklavier

News

Drobbins

ARM Rebuild

ARM systems will use new stage3's that are not compatible with earlier versions.
2015-06-27 by Drobbins
Drobbins

ABI X86 64 and 32

Funtoo Linux has new 32-bit compatibility libraries inherited from Gentoo. Learn about them here.
2015-06-18 by Drobbins
Drobbins

Pre-built kernels!

Funtoo stage3's are now starting to offer pre-built kernels for ease of install. read more....
2015-05-12 by Drobbins
More...

Xfce4-settings

Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.

xfce4-settings provides two main utilities used to configure key components of the XFCE desktop environment:

  • xfce4-settings-editor: Provides a dconf-editor-like interface used to configure components of XFCE ranging from Thunar to the XFCE notification daemon.
  • xfce4-settings-manager: Allows users to configure the same components as can be configured in the xfce4-settings-editor but provides a more easy to understand interface for configuration.

Installation

If you have already installed the XFCE desktop environment using the xfce4-meta package, xfce4-settings should be installed. Also, if you have installed an XFCE program such as thunar in another desktop environment or window manager such as Openbox or KDE, xfce4-settings is probably installed on your system too. If, for some reason, the program is not installed in either of those cases and you wish to emerge it, run the command:

# emerge xfce4-settings


After the emerge has finished, you can check that the package was successfully installed by running the command xfce4-settings-manager or by launching the program from your dock. If the package did install, you should be greeted with a window titled "Settings" that is divided into several sections with names like "Personal" and "Hardware." If the program does not launch after repeated attempts, consider filing a bug report at Funtoo Bugs.

Usage

To run xfce4-settings-manager in XFCE, navigate to the applications menu in your panel, go to "Settings" and then select "Settings Manager." Alternately, you can open your terminal emulator and type "xfce4-settings-manager" and press enter to launch the program. In other desktop environments, launch the program as you would any other.

Appearance (xfce4-appearance-settings)

Style

After clicking on the "Appearance" subsection in the section "Personal," you will find yourself in a tab titled "Style." This tab allows you to select the GTK+ theme that you would like to use from a list of themes that are currently installed in either /usr/share/themes or ~/.themes. The three colored boxes to the left of the theme name show the theme's colors. To select a GTK+ theme as default, simply click on it and your theme will change immediately.

Note

If the theme does not change when clicked, double check to see that you are launching XFCE with the --with-ck-launch parameter. Theming using xfce4-settings-manager does not seem to work without it.

Icons

To select the default icon theme for XFCE, click on the tab with the text "Icons." This tab, not surprisingly, allows you to edit your icon theme. To change your icon theme, click on the one that you like and the theme will change immediately. If it does not, read the above note.

Tip

To install new icon themes, extract an icon theme to either /usr/share/icons (for every user on the system) or to ~/.icons (for just you).

Fonts

To change the default font, the DPI value of the current font, or to enable font anti-aliasing, click on the "Fonts" tab. The default font can be changed quite easily by selecting the box under "Default Font." Selecting this box will bring up a list of all the different font families that are currently installed on your system, along with the available styles for each font family. To change your font, choose the appropriate font family, style, and size and the click the button labeled "OK" at the bottom right of the window. Your font should change immediately. If it does not, the above note may help to solve the problem. A nice default font is "Ubuntu Regular 10," provided by the ubuntu-font-family package which can easily be installed using the following command:

# emerge ubuntu-font-family

If you are unhappy with the scaling of the fonts in XFCE, perhaps because you are using a hiDPI display, consider increasing the value next to "Custom DPI setting." Finally, to make many fonts appear more crisp and well-defined, increase the value in "Hinting" to "Medium" or "Full."

Settings

If you do not like having images in menus or buttons or you would like to change the way that toolbars are displayed, navigate to the "Settings" tab. To modify how toolbars appear in GTK+ applications, modify the "Toolbar Style" dropdown to your pleasing. Here is what the different toolbar styles look like:

StylePreview
IconsXfce4-settings toolbar icons.png
TextXfce4-settings toolbar text.png
Text under iconsXfce4-settings toolbar text under icons.png

To add or remove images on GTK+ buttons, check or uncheck the checkbox adjacent to "Show images on buttons." To remove those pesky little icons in menus, uncheck "Show images in menus."

Desktop (xfdesktop-settings)

The desktop section of xfce4-settings is, not surprisingly, focused on the customization of the XFCE desktop. It includes options to customize the wallpaper, desktop icons, and desktop menus.

Background

The first tab of the desktop section is titled "Background." This tab provides configuration options for the wallpaper of your XFCE desktop. To change the wallpaper for the current desktop, take note of the directory in which you have stored the image that you want to set as your wallpaper ~/Pictures/Wallpapers/, for example. Then, click the box next to "Folder" in the bottom of the Background tab. When you click this box, you will get a menu displaying some directories where your photos could be located. If the picture you wish to use is not in any of the listed directories, select "Other..." and a dialog called "select a file will open." Now, navigate to the parent directory of the directory in which your wallpapers are stored (~/Pictures in my case) and click on the icon for that directory (should be called Wallpapers for me). After selecting that directory, click "Open" in the bottom right of the "Select a file" dialog. Now you should be able to choose the wallpaper that you wanted from the "Wallpaper for my desktop" box in the Background tab. To change to that wallpaper, simply click on the image of the desired wallpaper and your background should change immediately.

Menus

The "Menus" tab controls the appearance of menus that appear on your desktop when you right and middle click.

Icons

Clicking on the tab labeled "Icons" allows you to customize the appearance of desktop icons. If you do not like having icons on your desktop and have struggled to find a way to remove the "Home," "Filesystem," and "Trash" icons from your desktop, you're in luck! Go to the bottom of the configuration dialog and uncheck all of the boxes in the "Default Icons" box. One by one, those pesky little icons will fade away into the nothingness that they deserve. Conversely, if you love desktop icons, you can always add more by right clicking on your desktop and selecting the appropriate "Create *" option in the menu that appears.

To remove the large tooltips that appear when you hover over an icon on your desktop, uncheck the box "Show icon tooltips" in xfce4-settings. You can also shrink the size of the tooltip icon, and hence the tooltip itself, by decreasing the value in the box next to "Size:"

Warning

The rest of this page is still 'under construction.'

File Manager (thunar-settings)