MOVED: Difference between revisions

From Alpine Linux
Jump to navigation Jump to search
m (sort basics into a section)
(Avoid double redirect)
Tag: Redirect target changed
 
(81 intermediate revisions by 6 users not shown)
Line 1: Line 1:
<!-- Edited cmd blocks to indicate the user privileges required for each (ie with # or $) -->
#REDIRECT [[Xfce]]


[[file:XFCEScreenshot.png |thumb |Xfce screenshot.]]
Moved to https://wiki.alpinelinux.org/wiki/Xfce


= Initial setup =
{{Delete|Article title is asinine}}
Start by booting up Alpine (see [[Installation|these]] instructions on how to do that)<BR>
When Alpine is up and running, do the initial setup.
{{Cmd|# setup-alpine}}
 
= Install packages =
Ensure the "community" repository is enabled in ''/etc/apk/repositories''. 
Edit the file using ''vi'', and uncomment the line with ''community'' at the end.
{{Cmd|# vi /etc/apk/repositories}}
 
Update the local copies of the repositories.
{{Cmd|# apk update}}
 
== Basic packages ==
The ''[[Alpine_setup_scripts#setup-xorg-base | setup-xorg-base]]'' script allows to install the xorg base packages and to replace mdev with udev.
 
It also allows us to specify additional packages to install:
{{Cmd|# setup-xorg-base xfce4 xfce4-terminal lightdm-gtk-greeter xfce4-screensaver dbus-x11 sudo}}
So, this might take a few minutes to finish depending on your network speed.
 
== Video packages ==
You will most likely want to install driver packages with specific support for your video chipset. Otherwise, X will resort to the rather slow and cumbersome VESA standard driver.
 
To see available video driver packages run:
{{cmd|$ apk search xf86-video}}
 
For example, if you have an Sis video chipset install 'xf86-video-sis', for Intel video chipset install 'xf86-video-intel'.
 
{{Cmd|# apk add xf86-video-sis}}
and / or
{{Cmd|# apk add xf86-input-synaptics}}
 
Use xf86-video-modesetting for Qemu/KVM guests.
 
{{tip|Probably for KVM/Qemu guests you want to use ''qxl'' Video and Display ''Spice''. For this purpose install xf86-video-qxl on guest and run a Spice client on the host}}
 
Use xf86-video-vmware and xf86-video-vboxvideo for Virtualbox/VMware guests.
 
{{tip|If you want to run XFCE in an Oracle VM Virtual Box, you need to install the [[VirtualBox_guest_additions|VirtualBox guest additions]] as well. They contain parts of the driver, without them, XFCE won't start.}}
 
Use xf86-video-fbdev for Hyper-V guests.
 
{{tip|If you use Hyper-V, you should install the [[Hyper-V_guest_services|Hyper-V guest services]] as well.}}
 
Use xf86-video-geode for Alix1D.
 
== Input packages ==
 
To search for xf86-input driver packages run:
{{cmd|$ apk search xf86-input}}
 
As good choice for the start is:
 
{{cmd|# apk add xf86-input-mouse xf86-input-keyboard}}
 
{{Pkg|kbd}} may help if the <b>Numlock</b> service is added but does not start, or if <b>'setleds not found'</b> during the boot sequence:
 
{{cmd|# apk add kbd}}
 
= Configure xorg-server (optional) =
{{Tip|Refer to [[Qemu]] page if you are installing inside a Qemu/KVM virtual machine}}
 
On most systems, xorg should be able to autodetect all devices. However you can still configure xorg-server by hand by launching:
{{Cmd|# Xorg -configure}}
This will result in `/root/xorg.conf.new`. You can modify this file to fit your needs.<BR>
(When finished modifying and testing the above configuration file, move it to `/etc/X11/xorg.conf` for normal usage.)
 
== Keyboard Layout ==
If you use a layout different than "us", you need to:
{{Cmd|# apk add setxkbmap
setxkbmap <%a language layout from /usr/share/X11/xkb/rules/xorg.lst%>}}
In order to make it persistent add this section to /etc/X11/xorg.conf:
{{Cmd|Section "InputClass"
Identifier "Keyboard Default"
MatchIsKeyboard "yes"
Option "XkbLayout" "<%a language layout from /usr/share/X11/xkb/rules/xorg.lst%>"
EndSection}}
 
 
Another way to change the keymap when logging into X is to use ~/.xinitrc.  The following example loads a British keymap, simply add this line to the beginning of the file:
<code>setxkbmap gb &</code>
 
Note that you will need the "setxkbmap" package for this to work!
In addition you if you need to create the ~/.xinitrc file, add a second line like <code>exec startxfce4</code>
 
= Create user accounts =
Create a normal user account.
{{Cmd|# adduser -g 'Natanael Copa' ncopa}}
 
Optionally, give that user sudo permissions in /etc/sudoers. When doing so, it is important to use the command: {{Cmd|visudo}} This ensures that only one user is changing the file at any given time.  Visudo has two modes: Command mode and Insert mode.  To edit the file, use the arrows to navigate to the appropriate line and enter Insert mode by pressing the 'i' key.  To save and exit, enter Command mode by pressing the 'Esc' key, then ':w' + 'enter' to save, and finally ':q' + 'enter' to quit.
 
You may want to add the home directories to the lbu captures:
{{Cmd|#lbu include /home}}
 
= Start and enable dbus =
Depending on your setup procedure dbus probably isn't running at this point, which will lead to issues like missing icons and keyboard shortcuts.
 
Start dbus first.
{{Cmd|# rc-service dbus start}}
You will likely also want dbus to start on boot.
{{Cmd|# rc-update add dbus}}
 
= Start your desktop =
Start lightdm and log in with your new user.
{{Cmd|# rc-service lightdm start}}
 
Once you have verified that it actually works you can make lightdm start up at boot:
{{Cmd|# rc-update add lightdm}}
 
If you're missing icons on menus and bars install a theme:
{{Cmd|# apk add faenza-icon-theme}}
 
= Allowing shut down and reboot =
In order to allow the user to shut down the machine or reboot either {{Pkg|elogind}} and {{Pkg|polkit-elogind}}, or {{Pkg|polkit}} and {{Pkg|consolekit2}} needs to be installed:
 
{{Cmd|# apk add elogind polkit-elogind}}
 
Or:
 
{{Cmd|# apk add polkit consolekit2}}
 
= Installing fuse =
 
For browsing of network shares within XFCE that works seamlessly with file associations, you can install gvfs-fuse and the gvfs packages for the network protocols you use.  For instance, for SMB:
{{Cmd|# apk add gvfs-fuse gvfs-smb}}
 
Presently (3.11), the OpenRC script for fuse is a separate package.  However, it may be sufficient for GVfs to initiate the fuse kernel module:
{{Cmd|# apk add fuse-openrc}}
 
Then you can manually start the fuse service (you'll need to restart any XFCE sessions already in progress -- you can log them out and log in again):
{{Cmd|# rc-service fuse start}}
 
You can set the fuse service to start up automatically at boot:
{{Cmd|# rc-update add fuse}}
 
= Auto-mounting USB drives =
 
To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add thunar-volman udisks2}}
Also, make sure that mounting is enabled in
Thunar>Edit>Preferences>Advanced>Volume Management>Configure>Storage>Removable Storage
Packages below optional depending on what USB media you intend to mount:
{{Cmd|ntfs-3g: NTFS support
gvfs-mtp: media players and mobile devices that use MTP
gvfs-gphoto2: digital cameras and mobile devices that use PTP
gvfs-afc: Apple mobile devices}}
 
= Troubleshooting =
If you are unable to login, check /var/log/lightdm/lightdm.log, there may be output there from X to indicate failed modules, etc.
 
If your mouse / keyboard is not responding, try to install xf86-input-evdev (that will appeared in lightdm.log if you lack it). Or you can try to disable hotplug.
 
  Section "ServerFlags"
    Option "AutoAddDevices" "False"
  EndSection
 
If you Xorg server segfaults in kvm/qemu then add ''nomodeset'' as a boot option when booting up.
 
If you are unable to login, or you see an error "Failed to execute login command", you should check ~/.xinitrc (if you're using .xinitrc) with your preferred text editor (vi, nano, etc) and ensure that it is set to boot into xfce. To do this, the 'exec' line (usually the last line in the file) should read "exec startxfce4". If ~/.xinitrc does not exist, create it and add the exec line. this command will do it:
 
{{Cmd|$ echo "exec startxfce4" >> ~/.xinitrc}}
 
== Compositor ==
 
If you login to xfce once, logout, and then login again, and your panel and windows disappear or start flickering, this is because xfce is writing a default config file with the compositor enabled, but does not enable it during your first login.  Clear out the ~/.config/xfce directory, and login as "first time" again, as the default vblank setting for the compositor is likely incorrect.  Open the windows manager tweaks and dconf editor (or use dconf-query) before you log out.  Tick the compositor to off in the window manager tweaks ui.  If you have a recent enough xfce (4.14) there is a ui in window manager tweaks to set syncing mode, and you can try different values, such as vblank, xpresent, and glx, while turning the compositor on and off, until you find one that works.  Or, from dconf editor, you can set xfwm4 /general/vblank_mode, which you will find is set to "auto" by default, and then turn the compositor on again.  This can also be accomplished from the command line using using:
 
{{cmd|xfconf-query -c xfwm4 -p /general/vblank_mode -s mode}} where mode is vblank, glx or xpresent. 
 
You have to use xfconf-query from within the xfce terminal session, or at least with the xfce settings daemon started.
 
= =
* [http://troglobit.com/2017/09/10/install-x-window-in-alpine-linux/ Install X-Window in Alpine Linux] Joachim Nilsson 2017
 
[[Category:Xfce]]

Latest revision as of 09:05, 9 February 2022

Redirect to:

Moved to https://wiki.alpinelinux.org/wiki/Xfce

Tango-user-trash-full.png
This material is proposed for deletion ...

Article title is asinine (Discuss)
Make sure no other pages link here and check the page's history before deleting.