First of all, if you are unable to understand these instructions, please DO NOT install my packages, as I am not prepared to hold everyone's hand just so that they can have the latest and greatest version of Xfce. Notes on the Xfce package: 1. This package requires the vte, dbus, dbus-glib, and gamin packages that are also available from this repository - I am no longer going to maintain two different builds of Xfce, so if you want a version that runs on a vanilla 11.0 installation, the SlackBuild script and sources are available. NOTE: If you have some of these dependencies installed from elsewhere, most notably LinuxPackages.net, all bets are off. I do *not* make any promises that my stuff will peacefully coexist with theirs. You are on your own. 2. You will need to make sure the the messagebus service is started prior to launching Xfce - see the dbus package's information below for how to do that. 3. Back up your $HOME/.config directory before starting Xfce - the old 4.2.x configuration is not fully compatible with that of 4.4.x, so you will not be able to go back to Xfce-4.2.x and keep your configs unless you back them up. 4. Be sure to run 'xwmconfig' *before* starting Xfce after upgrading - this will copy the new xinitrc file into your $HOME/.xinitrc 5. The xarchiver archive manager that was present in the previous rc/beta versions was not shipped with 4.4.1 due to questions as to whether it was ready - did volkerdi join the Xfce development team? ;-) 6. Read this link if you don't like Firefox's behavior when clicking on hyperlinks in some other application: http://foo-projects.org/pipermail/xfce4-dev/2007-April/022912.html From the dbus package information: You will need to create the 'messagebus' user and group before installing the dbus package; sample lines to do so are below: groupadd -g 81 messagebus useradd -c 'System Message Bus' -g messagebus -u 81 -d / -s /bin/false messagebus Note that the numerical uid and gid given in the above sample lines may need to change on your system; if you already have an existing user and/or group with those id's, then they obviously need to be modified for your system. Because the 'messagebus' user and group are considered system accounts, the custom is to make their uid's and gid's less than 100, but that's entirely up to you. After creating the 'messagebus' user and group, you will need to make sure the /etc/rc.d/rc.messagebus script is run at boot. The easiest way to do this is adding something like the following line to /etc/rc.d/rc.local: if [ -x /etc/rc.d/rc.messagebus ]; then /etc/rc.d/rc.messagebus start fi You will also need to make sure the messagebus service is stopped on halt or reboot, or the stale pid file will be hanging around when the system comes back up and messagebus will fail to start (thanks to flujan for the report). On Slackware 11.0 and newer, you can add something like this to /etc/rc.d/rc.local_shutdown: if [ -x /etc/rc.d/rc.messagebus ]; then /etc/rc.d/rc.messagebus stop fi