Dit is een lijst met veel gestelde vragen over de Xfce bureaublad omgeving. Het is aan iedereen vrij om deze pagina te verbeteren of uit te bereiden, maar hou het schoon en leesbaar voor andere Xfce gebruikers.
Xfce is een bureaublad omgeving voor Unix en andere Unix-achtige platformen, zoals Linux, Solaris of BSD. De ontwerp filosofie is „Ontworpen voor productiviteit. Het laadt en draait snel, terwijl het tegelijkertijd systeembronnen spaart.” (Olivier Fourdan) en zou iedereen moeten aanspreken die kijkt naar een snelle, moderne, en efficiënte werkplek op een *NIX machine.
Eks, Ef See Ee. De naam Xfce stond oorspronkelijk voor XForms Common Environment, maar sindsdien is Xfce tweemaal herschreven, en het maakt nu geen gebruik meer van de XForms toolkit. De naam wordt nog steeds gebruikt, maar wordt niet meer geschreven als 'XFce', maar 'Xfce'. Op dit moment heeft het acroniem geen betekenis. (Suggestie: X Freakin' Cool Environment)
Zag je het echt niet?? Je maakt een grapje… het is een muis, voor alle overduidelijke redenen zoals Wereld Overheersing en andere monsters.
Xfce is ontwikkeld met de gedachte aan veelzijdigheid. Het wordt op dit moment ondersteund op Linux, Solaris en BSD.
Xfce 4 componenten vallen onder de open source licenties, GPL of BSDL voor applicaties en LGPL of BSDL voor libraries. Zie de documentatie, de source code of de xfce website (http://www.xfce.org) voor meer informatie.
Xfce kan op ten minste drie verschillende manieren worden geinstalleerd.
Some distributions have separate -devel packages for libraries. The Xfce installer needs those package for compiling the Xfce desktop environment. When, for example, the dependency for glib is missing, make sure you have both the glib and the glib-devel package installed.
This error message tells you that the configure script was unable to verify that the C++ preprocessor is setup properly on your system. You can most probably fix this problem by installing the g++ package for your distribution.
For some reason the installation wizard is not able to connect to an Xserver, which is required for the installer. This usually happens when you use su, and su in turn doesn't pass the DISPLAY environment variable properly. Try to use the commands:
$ xhost +localhost $ su --preserve-environment # ./xfce4-184.108.40.206-installer.bin
$ xhost +localhost $ su # env DISPLAY=:0 ./xfce4-220.127.116.11-installer.bin
Instead (replace :0 with your display name if required).
There are three different ways to do this:
exec startxfce4to your
.xinitrcin your home directory and simply use
if [ "$(tty)" = "/dev/tty1" -o "$(tty)" = "/dev/vc/1" ] ; then startxfce4 fi
If you installed Xfce system-wide and you want to use the GNOME Display Manager (gdm) to start your Xfce session, you will have to create a .desktop file to teach gdm how to start the Xfce session. This is a sample desktop file, Xfce.desktop:
[Desktop Entry] Encoding=UTF-8 Name=Xfce 4.4 Session Comment=Use this session to run Xfce 4.4 as your desktop environment Exec=/usr/local/bin/startxfce4 Icon=/usr/local/share/pixmaps/xfce4_xicon1.png Type=Application
It is usually enough to simply copy the example file to the Session directory used by gdm; this directory is usually located in /etc/dm/Sessions, /etc/X11/gdm/Sessions, /usr/share/xsessions, /usr/X11/share/gnome/xsessions or some other location, refer to the documentation of your system for details. You need to restart gdm after you created the file.
If you installed Xfce system-wide and you want to use the KDE Display Manager (kdm) to start your Xfce session, you will have to create a .desktop file to teach kdm how to start the Xfce session.
First you need to find where kdm searches for its .desktop files:
Common locations are /usr/share/apps/kdm/sessions or /usr/local/share/kdm/sessions. Once you found the kdm session directory, you need to create a new file Xfce.desktop with the following:
[Desktop Entry] Encoding=UTF-8 Type=XSession Exec=/usr/local/bin/startxfce4 TryExec=/usr/local/bin/startxfce4 Name=Xfce 4.4 Comment=The Xfce 4.4 Desktop Environment
Xfce simply wants for your hostname to be in
/etc/hosts. Example input:
Assign a key with the Keyboard Settings → Shortcuts to the command
xfdesktop -menu. The menu will popup where your mouse is located. You can also use
xfce4-popup-menu to popup the panel menu (also provided by xfdesktop and make sure you have the plugin in your panel ^_~).
Assign a key to the command
The windows button (also known as the superkey) not working as a modifier is related to the toolkit, GTK+ in the case of Xfce. If you want to have the windows-key working we recommend you to upgrade GTK+ to at least version 2.10.0.
There are two possibilities to achieve this. Or you should use a display manager that turns the numlock on (eg. gdm, check the settings) or you can use a little program called numlockx, adding
numlockx on in your .xinitrc will do the job.
Use xmodmap to assign keycodes to your Media keys to make them available for the Xfce shortcut editor:
To determine keycodes of the multimedia keys use the program
xev. Create a
.Xmodmap file in your $HOME directory containing those keycodes and assign keysyms to them. Example:
keycode 162 = XF86AudioPlay keycode 164 = XF86AudioStop keycode 160 = XF86AudioMute keycode 144 = XF86AudioPrev keycode 153 = XF86AudioNext keycode 176 = XF86AudioRaiseVolume keycode 174 = XF86AudioLowerVolume
All possible keysyms can be found in /usr/lib/X11/XKeysymDB or /usr/share/X11/XKeysymDB. To ensure that the .Xmodmap file is loaded when you start Xfce add
/usr/bin/xmodmap $HOME/.Xmodmap to your
.xprofile file. When you start the shortcut editor the assigned keysyms should show up when you press one of your multimedia keys. Now it is possible to assign a command to them.
There are several options. One is to use
xfce4-kbd-plugin, see http://goodies.xfce.org/projects/panel-plugins/xfce4-xkb-plugin . You can also use the
setxkbmap command with the two letter keyboard code as argument; you can edit your X server configuration file to choose a different keyboard layout (change the value after
Option „XkbLayout”, e.g.:
Option „XkbLayout” „dvorak”).
Yes, of course… Keyboard shortcuts are defined on two locations. The shortcuts to handle the window manager are defined in the Settings Manager > Window Manager Settings > Keyboard. The
Default theme can not be changed, but when you add a theme you can change that one. More global keyboard shortcuts, like volume adjustements, can be found in Settings Manager > Keyboard Preferences > Shortcuts. Again you need to add a new theme before you can start customizing it.
The left-button single-click menu button display speed is linked to the double click speed. If one wants the menu to appear quicker, just change the double click speed in the Xfce 4 Settings Manager Mouse properties to be faster. Or, one can right click on the title bar to get the menu displayed almost instantly without adjusting the double-click speed. The menu will display both ways.
There are two possibilities. The first is by middle clicking on the desktop (if you have xfdesktop running) or you can add the window list plugin to the panel.
cp ~/.cache/xfce4/desktop/menu-cache-name-of-the-generated-file.xml ~/.config/xfce4/desktop/menu2.xml cd ~/.config/xfce4/desktop/ cat menu.xml > menu3.xml cat menu2.xml >> menu3.xml mv menu.xml menu.orig.xml mv menu3.xml menu.xml
Now, you already have a menu with all the categories in the main tree with some duplicates, but you must first edit menu.xml with your favorite editor and remove the 4 following lines in the middle of the file, otherwise the menu editor will complain about a wrong format:
</xfdesktop-menu> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE xfdesktop-menu> <xfdesktop-menu>
That's all. Now you can run the menu editor, remove the few duplicates and edit all as you like.
Settings > Desktop > Menu > Menu Editor
Notes: by removing the „system” line, you will remove all the duplicates menu entries from the auto generated file. So, if it is changed in this auto generated file, they don't appear anymore, but you will get rid of most of the duplicates.
To restore the original menu, just do in a terminal:
mv menu.xml menu3.xml; mv menu.orig.xml menu.xml
No, you can not.
Though there are many users who would like to see this feature implemented, here's the reason it is not going to happen: 'There are users that seem to use their trash as their default storage system, as a consequence it can happen that they crawl behind your computer. They see no harm in removing files they created since they are in trash. But when they accidently select one or two files belonging to you, you wish there was.'
With the introduction of trash-can support in any file-manager there came careless users. Thunar has trash-support too to protect you from them.
Thunar allows you to edit menu accelerators by simply hovering over the chosen action and by clicking the new keyboard shortcut you want to assign. To activate the editable menu accelerators select the „Editable menu accelerators” entry in the User Interface Settings plugin.
You will find your deleted items in
Two possible ways. First, You'll need to build thunar with support for gconf (GNOME thumbnailers) and install one of the available movie thumbnailers for GNOME, i.e. Totem includes the totem-video-thumbnailer. Second, You can get thumbnails without GNOME by installing thunar-thumbnailers plugin.
Yes, in Xfce 4.4 you can hide some of the desktop icons. You can read more about those hidden settings here.
./configure –enable-thunar-vfs –enable-exo)
The Xfce Window Manager has a feature called smart placement which can be adjusted based on the window size. Basically it will automatically center windows that are below a certain size and once they get bigger than that, new windows will try to be arranged automatically in the best place to have coverage. You can adjust the minimum size setting under Settings → Window Manager Tweaks → Placement.
Short answer: no.
Long answer: If the application supports it, it will restore itself at the location you last specified in the size you last specified (example: Terminal or Thunar). If the application doesn't support it you can use a window matching application like
There are two possible reasons why the application is started: It is saved in the last session or it is listed in the auto started applications. Follow 1 of the two steps below to get rid of the applications.
xfce4-autostart-editorand remove the application(s). You can also manually delete those files in
~/.cache/sessions/directory when you're not logged in.
There are two way to fix this:
You have to allow the user(s) to execute
$installdir/libexec/xfsm-shutdown-helper with sudo. Install sudo and run
visudo (root) and add the following line (replace prefix with the correct path):
%users ALL = NOPASSWD:<prefix>/libexec/xfsm-shutdown-helper
Add the user to the users group (root):
gpasswd -a <username> users
When you logout and login again, the shutdown and restart buttons should be sensitive. For more information you can referrer to the xfce4-session and sudo documentation.
Make sure that the hal and dbus daemons are started on boot. Refer to your distribution for exact steps.
Your /etc/dbus-1/system.d/hal.conf should contain a section similar to this:
<policy group="power"> <allow send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/> ... </policy>
Add the user to the
power group (root):
gpasswd -a <username> power
When you logout and login again, the shutdown and restart buttons should be sensitive.
Enable the toggle button Prompt on logout in the session manager settings.
Just don't run it at startup…
xftaskbar4line in your
If you select this option, the window-manager will show an hourglass while the program is loading. The startup-notification libraries have to be installed. They are probably available with your distribution. This feature is only supported by modern applications (Gtk2.x and Qt3.x based).
As Xfce is modular by design all of those visual elements are actually separate processes. You can just start their process again to regain them. If you want to make sure that they are started again next time you login you should check the „Save session for future logins” in the logout dialog.
There are at least 4 possibilities:
The gtk-xfce-engine-2 package has to be installed using same prefix as Gtk2 itself. When installed from sources, the engine is, by default, installed in /usr/local, while Gtk2 is often installed in /usr. Just install gtk-xfce-engine-2 again using
./configure –prefix=/usr, and the themes will hopefully become available.
You can read everything about changing themes in the Tips & Tricks section of the wiki.
Enable the Composite extension in the X11 config file and make use Xfwm4 is compiled with compositor support (
Section "Extensions" Option "Composite" "Enable" EndSection
Once this is activated, go to
Settings > Panel and
Settings > Window Manager Tweaks.
NVidia users also need (well it's recommended) this in the
device section of the card:
Option "RenderAccel" "true" Option "AllowGLXWithComposite" "true"
It's not possible. This setting has to be managed by the application itself.
First, try another Gtk theme, since some themes override the color. If it doesn't solve the problem, you probably have an old ~/.gtkrc-2.0 : remove it and try again.
In order to improve focus management this option was removed.
You can report bugs here or ask on the mailing lists or forums for help. If you want to report a bug please read the Xfce debug guide and the Gaim gdb how to to ensure your bug report actually makes sense and is useful.
Whenever we feel like it is ready to be released. If you are unhappy with this you can always choose to hire the whole Xfce developer crew and pay us (we accept VISA/MasterCard, but not American Express)… Then we can even tailor it to your liking…