Latest revision as of 13:00, 20 September 2024

Gnome Desktop aims to get things done with ease, comfort, and control.

Note: Before installing any desktop,

Create a non-privileged user account for security reasons, if you skipped this step during Installation.
Enable community repository. Setup-desktop script automatically does this for you.
Install graphics driver for your video hardware.

Installation using setup-desktop

The Alpine Linux script for setting up a desktop quickly is setup-desktop.

# setup-desktop

On running the above command, you will be prompted to select a desktop environment.

Which desktop environment? ('gnome', 'plasma', 'xfce', 'mate', 'sway' or 'none') [none]

Once you have chosen a desktop environment, this script installs the chosen desktop along with all the necessary packages, firefox browser and adds the necessary services to run on startup. You can reboot when complete and the system will boot into a graphical login screen with the desktop environment. Depending on the desktop chosen, the script also activates the necessary services like dbus, elogind, login manager etc..

To view all the packages that are installed by the script for the chosen desktop you can issue the below command:

# cat /sbin/setup-desktop

When gnome is chosen, the above utility also installs Pipewire for audio and gdm as display manager.

Installing Additional packages

If you want, you can install additional GNOME apps for a more complete GNOME experience with:

# apk add gnome-apps-extra

And even all of GNOME games with:

# apk add gnome-games-collection

Enabling GNOME Shell screen recording

For the embedded screen recording in GNOME Shell to work, you will need some additional packages:

# apk add pipewire wireplumber gst-plugin-pipewire

Enabling GNOME Software

For GNOME Software to be able to manage APK packages, it needs the apk-polkit-server service working. To enable it and start it up:

# rc-update add apk-polkit-server default && rc-service apk-polkit-server start

Updating GNOME packages

Most GNOME apps and core systems follow a common versioning pattern, and have a similar release cadence. In order to reduce the workload on maintainers, the gnome-aports-utils project exists. It contains a series of scripts that can be used to detect changes on GNOME-related projects, and commit them. When doing major GNOME updates, and doing minor updates on many projects, these scripts can help warranty that no project is forgotten, and reduce the time needed to build and test the upgrades. We recommend everybody to use and contribute to that repository instead of pushing updates for every GNOME component individually.

Major GNOME upgrade

About every half year, GNOME publishes a new major release. These are announced at: https://release.gnome.org/calendar/ (note the dates are the tarball-due-dates and not the actual release drop).

With this release the whole GNOME stack gets upgraded, this includes G-related libraries, the GNOME shell with mutter, GNOME core apps and other packages following the same schedule. The GNOME release engeneering team publishes dates for alpha, beta, release candidates and stable versions for every major version, most GNOME core packages follow their schedules, but not all of them. Announcements of the releng team are posted on the GNOME forum (https://discourse.gnome.org/tag/release-team) and Release Notes for each phase (with it's upgraded packages) are at: https://download.gnome.org/core/

Therefore we should also upgrade along the dependency tree (glib -> gtk4 -> mutter -> gnome-shell -> other apps). Most important libraries are glib, gtk4, libadwaita. These are mostly already released in the alpha-phase and don't contain many breaking changed. To upgrade other GNOME core package to the latest version in a major version, you can use gnome-aports-utils or also check https://download.gnome.org/sources (sorted by date) (thats where all GNOME core maintainers upload their tarballs).

Also take a look at Gentoo's upgrading guide: https://wiki.gentoo.org/wiki/Project:GNOME/GNOME_Bumping_Guide

Troubleshooting

If you are unable to log in, check /var/log/gdm/greeter.log, there may be info there from X that indicates failed modules, etc.

If GNOME Terminal doesn't start, add the following to /etc/profile.d/locale.sh: LANG=en_US.UTF-8 and reboot.

If the on-screen keyboard shows up in GDM after installing other UIs such as Phosh, you need to disable it by opening the Accessibility menu (top right) when you are in the GDM login screen. You can disable the on-screen keyboard there. Or set org.gnome.desktop.a11y.applications screen-keyboard-enabled to false for the gdm user with dconf

Slow applications or rendering issues

Please note that some applications, i.e. Gnome Web (Epiphany), may require the installation of libraries related to hardware acceleration to work correctly.

In quite some cases, this can be solved by installing mesa-gles (OpenGL ES). Check if you you have issues loading the shared library libGLESv2.so.2. If so, you can install it with:

# apk add mesa-gles

@@ Line 1: / Line 1: @@
-= Initial setup =
+[https://www.gnome.org/ Gnome Desktop] aims to get things done with ease, comfort, and control.
-Start by booting up Alpine (see [[Installation|these]] instructions on how to do that)<BR>
-When you Alpine is up and running, do the initial setup.
-{{Cmd|# setup-alpine}}
-{{Cmd|# setup-xorg-base}}
-= Installing packages =
+{{:Include:Setup-desktop}}
-Install basic desktop system and gnome packages. As of right now, these are in the testing repo.<BR>
-This might take a few minutes depending on your network speed.
-{{Cmd|# apk add gnome}}
-<BR>
-If you want to you can also install additional GNOME apps for a more complete GNOME experience with:<BR>
+When gnome is chosen, the above utility also installs [[PipeWire|Pipewire]] for audio and [[gdm]] as display manager.
-{{Cmd|# apk add gnome-apps}}
-<BR>
-== Setting up udev ==
+= Installing Additional packages =
-You'll have to enable udev in order for GNOME to function properly.
-{{Cmd|# apk add udev
+If you want, you can install additional GNOME apps for a more complete GNOME experience with:
-# /etc/init.d/udev start && /etc/init.d/udev-trigger start && /etc/init.d/udev-settle start
+{{Cmd|# apk add gnome-apps-extra}}
-# rc-update add udev sysinit
-# rc-update add udev-trigger sysinit
-# rc-update add udev-settle sysinit
-}}
-== Setting up Xorg ==
+And even all of GNOME games with:
-Even when using GNOME Wayland you'll still need a setup Xorg for XWayland.
+{{Cmd|# apk add gnome-games-collection}}
-=== Video packages ===
+= Enabling GNOME Shell screen recording =
+For the embedded screen recording in GNOME Shell to work, you will need some additional packages: {{cmd|# apk add pipewire wireplumber gst-plugin-pipewire}}
-{{cmd|$ apk search xf86-video}}
+= Enabling GNOME Software =
+For GNOME Software to be able to manage APK packages, it needs the <code>apk-polkit-server</code> service working. To enable it and start it up:
+{{cmd|# rc-update add apk-polkit-server default && rc-service apk-polkit-server start}}
-Then install the driver matching to your card, e.g. if you have an Intel iGPU:
+= Updating GNOME packages =
-{{cmd|# apk add xf86-video-intel}}
+Most GNOME apps and core systems follow a common versioning pattern, and have a similar release cadence. In order to reduce the workload on maintainers, the [https://gitlab.alpinelinux.org/pabloyoyoista/gnome-aports-utils gnome-aports-utils] project exists. It contains a series of scripts that can be used to detect changes on GNOME-related projects, and commit them. When doing major GNOME updates, and doing minor updates on many projects, these scripts can help warranty that no project is forgotten, and reduce the time needed to build and test the upgrades. We recommend everybody to use and contribute to that repository instead of pushing updates for every GNOME component individually.
-=== Input packages ===
+== Major GNOME upgrade ==
-Usually libinput is the best choice, as it's integrated best with GNOME and offers advanced functionality (e.g. palm rejection for touchpads).
+About every half year, GNOME publishes a new major release. These are announced at: https://release.gnome.org/calendar/ (note the dates are the tarball-due-dates and not the actual release drop).
-{{cmd|# apk add xf86-input-libinput}}
+With this release the whole GNOME stack gets upgraded, this includes G-related libraries, the GNOME shell with mutter, [https://apps.gnome.org/ GNOME core apps] and other packages following the same schedule. The [https://matrix.to/#/%23release-team:gnome.org GNOME release engeneering team] publishes dates for alpha, beta, release candidates and stable versions for every major version, most GNOME core packages follow their schedules, but not all of them. Announcements of the releng team are posted on the GNOME forum (https://discourse.gnome.org/tag/release-team) and Release Notes for each phase (with it's upgraded packages) are at: https://download.gnome.org/core/
-= Starting your desktop =
+Therefore we should also upgrade along the dependency tree (glib -> gtk4 -> mutter -> gnome-shell -> other apps). Most important libraries are glib, gtk4, libadwaita. These are mostly already released in the alpha-phase and don't contain many breaking changed. To upgrade other GNOME core package to the latest version in a major version, you can use [https://gitlab.alpinelinux.org/pabloyoyoista/gnome-aports-utils gnome-aports-utils] or also check [https://download.gnome.org/sources/?C=M&O=D https://download.gnome.org/sources (sorted by date)] (thats where all GNOME core maintainers upload their tarballs).
-Start GDM and login with your user.
-{{Cmd|rc-service gdm start}}
-Once you have verified that it actually works you can make gdm start up at boot:
+Also take a look at Gentoo's upgrading guide: https://wiki.gentoo.org/wiki/Project:GNOME/GNOME_Bumping_Guide
-{{Cmd|rc-update add gdm}}
 = Troubleshooting =
-If you are unable to login, check /var/log/gdm/greeter.log, there may be output there from X to indicate failed modules, etc.
+If you are unable to log in, check /var/log/gdm/greeter.log, there may be info there from X that indicates failed modules, etc.
+If GNOME Terminal doesn't start, add the following to /etc/profile.d/locale.sh: <code>LANG=en_US.UTF-8</code> and reboot.
+If the on-screen keyboard shows up in GDM after installing other UIs such as Phosh, you need to disable it by opening the Accessibility menu (top right) when you are in the GDM login screen. You can disable the on-screen keyboard there. Or set <code>org.gnome.desktop.a11y.applications screen-keyboard-enabled</code> to <code>false</code> for the <code>gdm</code> user with <code>dconf</code>
+== Slow applications or rendering issues ==
+Please note that some applications, i.e. Gnome Web (Epiphany), may require the installation of libraries related to hardware acceleration to work correctly.
+In quite some cases, this can be solved by installing <code>mesa-gles</code> (OpenGL ES). Check if you you have issues loading the shared library <code>libGLESv2.so.2</code>. If so, you can install it with:
+{{Cmd|# apk add mesa-gles}}
+== See also ==
+* [https://wiki.archlinux.org/title/GNOME GNOME - Archwiki]
+* [https://wiki.gentoo.org/wiki/GNOME GNOME - Gentoo Wiki]
+* [https://wiki.postmarketos.org/wiki/GNOME GNOME - PostmarketOS Wiki]
 [[Category:Desktop]]
+[[Category:Desktop Environments]]