GNOME: Difference between revisions

From Alpine Linux
m (Added steps for adding community repo and bash so users can get a terminal to work.)
(26 intermediate revisions by 10 users not shown)
Line 1: Line 1:
= Initial setup =
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}}


= Prerequisites =


= Enable Community Repository =
* [[Installation|Install]] AlpineLinux
[[Enable Community Repository|How to Enable the Community Repository]]
* [[Setting_up_a_new_user#Creating_a_new_user|Create a user account]] (optional but recommended)
* [[Repositories#Enabling_the_community_repository|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]] (no longer needed if installing GNOME through "setup-desktop")
 
{{Note|[[Wayland]] can be used but may be less stable and Gnome may still require Xorg}}


= Installing packages =
= Installing packages =
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>
Install basic desktop system and gnome packages.
{{Cmd|# apk add gnome-apps}}
{{Cmd|# setup-desktop gnome}}
<BR>


== Setting up udev ==
It will take care of installing the basic packages and setting up the display manager.  
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 terminal apps =
If you want to use the gnome-terminal/other terminal applications you will need to install bash. If you want a typical bash setup also enable bash completion:
{{cmd|# apk add bash}}
{{cmd|# apk add bash-completion}}


{{cmd|$ apk search xf86-video}}
= 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 pipewire-media-session gst-plugin-pipewire}}


Then install the driver matching to your card, e.g. if you have an Intel iGPU:
= Troubleshooting =
 
If GDM does not start with no logs generated at /var/log/gdm, try setting up udev: {{cmd|# setup-devd udev}}
{{cmd|# apk add xf86-video-intel}}
 
=== Input packages ===
 
Usually libinput is the best choice, as it's integrated best with GNOME and offers advanced functionality (e.g. palm rejection for touchpads).
 
{{cmd|# apk add xf86-input-libinput}}


= Starting your desktop =
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.
Start GDM and login with your user. You need a user other than root for this to succeed, since GDM will refuse starting if no user accounts (meaning accounts with a UID >= 1000) are available.
{{Cmd|rc-service gdm start}}


Once you have verified that it actually works you can make gdm start up at boot:
If logging in from GDM kicks you back to the login screen, try {{cmd|# apk add bash}} (bug report: #10953 sorry cannot link yet)
{{Cmd|rc-update add gdm}}


If you want to use the gnome-terminal/other terminal applications you will need to install bash. If you want a typical bash setup also enable bash completion:
If GNOME Terminal doesn't start, add the following to /etc/locale.conf: LANG=en_US.UTF-8 and reboot.
{{cmd|# apk add bash}}
{{cmd|# apk add bash-completion}}
 
= 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 logging in from GDM returns to logging screen, try {{cmd|# apk add bash}} (bug report: #10953 sorry cannot link yet)
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>


[[Category:Desktop]]
[[Category:Desktop]]

Revision as of 15:48, 1 August 2022

Prerequisites

Note: Wayland can be used but may be less stable and Gnome may still require Xorg

Installing packages

Install basic desktop system and gnome packages.

# setup-desktop gnome

It will take care of installing the basic packages and setting up the display manager.

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 terminal apps

If you want to use the gnome-terminal/other terminal applications you will need to install bash. If you want a typical bash setup also enable bash completion:

# apk add bash

# apk add bash-completion

Enabling GNOME Shell screen recording

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

# apk add pipewire pipewire-media-session gst-plugin-pipewire

Troubleshooting

If GDM does not start with no logs generated at /var/log/gdm, try setting up udev:

# setup-devd udev

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 logging in from GDM kicks you back to the login screen, try

# apk add bash

(bug report: #10953 sorry cannot link yet)

If GNOME Terminal doesn't start, add the following to /etc/locale.conf: 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