kookie
/
nomicon
1
0
Fork 0
Code Issues Projects Releases 1 Activity
My personal project and infrastructure archive
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
391972 Commits
7 Branches
1 Tag
1.4 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 52e4445b26
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '52e4445b26'
${ noResults }
nomicon/infra/libkookie/nixpkgs/unstable/nixos/doc/manual/configuration/xfce.chapter.md

1.8 KiB
Raw Blame History

Xfce Desktop Environment

To enable the Xfce Desktop Environment, set

services.xserver.desktopManager.xfce.enable = true;
services.xserver.displayManager.defaultSession = "xfce";

Optionally, picom can be enabled for nice graphical effects, some example settings:

services.picom = {
  enable = true;
  fade = true;
  inactiveOpacity = 0.9;
  shadow = true;
  fadeDelta = 4;
};

Some Xfce programs are not installed automatically. To install them manually (system wide), put them into your from pkgs.xfce.

Thunar

Thunar (the Xfce file manager) is automatically enabled when Xfce is enabled. To enable Thunar without enabling Xfce, use the configuration option instead of simply adding pkgs.xfce.thunar to .

If you'd like to add extra plugins to Thunar, add them to . You shouldn't just add them to .

Troubleshooting

Even after enabling udisks2, volume management might not work. Thunar and/or the desktop takes time to show up. Thunar will spit out this kind of message on start (look at journalctl --user -b).

Thunar:2410): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported

This is caused by some needed GNOME services not running. This is all fixed by enabling "Launch GNOME services on startup" in the Advanced tab of the Session and Startup settings panel. Alternatively, you can run this command to do the same thing.

$ xfconf-query -c xfce4-session -p /compat/LaunchGNOME -s true

A log-out and re-log will be needed for this to take effect.