注意：

The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.

Difference between revisions of "GNOME First Steps"

From Funtoo
Jump to navigation Jump to search
(fix for gnome stage3)
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<languages/>
<translate>
<!--T:1-->
<blockquote>
<blockquote>
GNOME 3 is an easy and elegant way to use your computer. It is designed to put you in control and bring freedom to everybody. GNOME 3 is developed by the GNOME community, a diverse, international group of contributors that is supported by an independent, non-profit foundation. [http://gnome.org GNOME]
GNOME 3 is an easy and elegant way to use your computer. It is designed to put you in control and bring freedom to everybody. GNOME 3 is developed by the GNOME community, a diverse, international group of contributors that is supported by an independent, non-profit foundation. [http://gnome.org GNOME]
</blockquote>
</blockquote>


=== Prerequisites ===  
=== Prerequisites === <!--T:2-->
Before attempting to emerge Gnome, make sure that you have installed and tested the [[X Window System]] on your computer.
Before attempting to emerge Gnome, make sure that you have installed and tested the [[X Window System]] on your computer.


=== Preparing to emerge ===
=== Preparing to emerge === <!--T:3-->


<!--T:4-->
After verifying that you have installed the X Window system on your computer, change your system flavor to desktop, and enable the gnome profile mix-in. To accomplish this, run the following:
After verifying that you have installed the X Window system on your computer, change your system flavor to desktop, and enable the gnome profile mix-in. To accomplish this, run the following:
{{console|body=
{{console|body=
Line 15: Line 19:
By enabling the gnome mix-in, various settings, including the {{c|USE}} portage variable, will be optimized to provide you with a relatively painless Gnome install.
By enabling the gnome mix-in, various settings, including the {{c|USE}} portage variable, will be optimized to provide you with a relatively painless Gnome install.


=== Optional Wayland Support ===
=== Optional Wayland Support === <!--T:5-->


<!--T:6-->
With release-1.3, it is now possible to use Wayland instead of X as your display technology. If you would like to enable this -- it is optional -- you must also run the following command:
With release-1.3, it is now possible to use Wayland instead of X as your display technology. If you would like to enable this -- it is optional -- you must also run the following command:


<!--T:7-->
{{console|body=
{{console|body=
###i## epro mix-ins +wayland
###i## epro mix-ins +wayland
Line 24: Line 30:
{{Warning|While wayland is supported in Funtoo, wayland itself is not considered to be mature and most people will experience better results using X rather than wayland.}}
{{Warning|While wayland is supported in Funtoo, wayland itself is not considered to be mature and most people will experience better results using X rather than wayland.}}


When using Wayland, if you are using nvidia-drivers, you must manually enable KMS by adding the following to your {{c|params}} in {{f|/etc/boot.conf}}: {{c|1=nvidia-drm.modeset=1}}. KMS must be enabled ''manually'' when using nvidia-drivers.
<!--T:8-->
When using Wayland, if you are using nvidia-drivers, you must manually enable NVIDIA's own KMS by adding the following to your {{c|params}} in {{f|/etc/boot.conf}}: {{c|1=nvidia-drm.modeset=1}}. KMS must be enabled ''manually'' when using nvidia-drivers.


Also note that if using nouveau, our debian-sources-lts doesn't support NVIDIA GTX 1060 and later GPUs. If you have an NVIDIA GTX 1060 or later GPU, you will need to use the binary nvidia-drivers or use a newer kernel such as debian-sources.
=== X or Wayland === <!--T:9-->


=== Emerging ===
<!--T:10-->
You will want to make sure you run {{c|etc-update}} or {{c|dispatch-conf}} to update your configuration files after everything emerges. In particular, take a look at {{f|/etc/gdm/custom.conf}} and ensure that the following setting is configured to match whether or not you are running Wayland. This controls whether or not gdm runs using Wayland. If gdm starts in Wayland, then it is able to launch either X or Wayland sessions. If Wayland is disabled in gdm, then it will only be able to start X sessions.
 
<!--T:11-->
{{file|name=/etc/gdm/custom.conf|body=
[daemon]
WaylandEnable=true
}}


=== Emerging === <!--T:12-->
<!--T:13-->
The Funtoo Linux repositories include two ebuild "meta packages" that can be used to install Gnome. One of them, {{c|gnome-light}} installs a bare-bones gnome desktop with few "extra" applications and games that can be found in the {{c|gnome-extra}} and {{c|games-*}} portage categories, respectively. If you are interested in having a Gnome desktop with extra applications like a photo viewer, text editor, sound player, font viewer, etc, immediately after installing the Gnome packages, consider emerging the {{c|gnome}} package instead of {{c|gnome-light}}.
The Funtoo Linux repositories include two ebuild "meta packages" that can be used to install Gnome. One of them, {{c|gnome-light}} installs a bare-bones gnome desktop with few "extra" applications and games that can be found in the {{c|gnome-extra}} and {{c|games-*}} portage categories, respectively. If you are interested in having a Gnome desktop with extra applications like a photo viewer, text editor, sound player, font viewer, etc, immediately after installing the Gnome packages, consider emerging the {{c|gnome}} package instead of {{c|gnome-light}}.
{{Note|Individual Gnome applications can be installed on top of a {{c|gnome-light}} installation, allowing you to only install the applications you need and limit unnecessary bloat.}}
{{Note|Individual Gnome applications can be installed on top of a {{c|gnome-light}} installation, allowing you to only install the applications you need and limit unnecessary bloat.}}
Line 65: Line 82:
{{TableEnd}}
{{TableEnd}}


<!--T:14-->
The steps that should be followed to emerge GNOME are as follows:
The steps that should be followed to emerge GNOME are as follows:


<!--T:15-->
{{console|body=
{{console|body=
###i## emerge -auDN @world
###i## emerge -auDN @world
Line 72: Line 91:
}}
}}


{{Important|Make sure your {{c|VIDEO_CARDS}} setting in {{f|/etc/make.conf}} is set appropriately. This is needed even if you are using wayland.}}


=== A few finishing touches ===
=== A few finishing touches === <!--T:16-->


=== X or Wayland ===


You will want to make sure you run {{c|etc-update}} or {{c|dispatch-conf}} to update your configuration files after everything emerges. In particular, take a look at {{f|/etc/gdm/custom.conf}} and ensure that the following setting is configured to match whether or not you are running Wayland. This controls whether or not gdm runs using Wayland. If gdm starts in Wayland, then it is able to launch either X or Wayland sessions. If Wayland is disabled in gdm, then it will only be able to start X sessions.
==== Proprietary NVIDIA drivers ==== <!--T:17-->


{{file|name=/etc/gdm/custom.conf|body=
<!--T:18-->
[daemon]
While many video drivers (those that are part of xorg-x11) do not require users to be part of the {{c|video}} group for hardware acceleration, the proprietary NVIDIA drivers definitely do require this. Please make sure that any non-root user is part of the {{c|video}} group, and ensure that Nouveau kernel modules are blacklisted. Setup steps for proprietary NVIDIA drivers can be found on the  [[Package:NVIDIA_Linux_Display_Drivers|the NVIDIA Linux Display Drivers page]].
WaylandEnable=true
}}


==== OpenGL ====
==== Other Graphics Drivers ==== <!--T:29-->


GNOME uses OpenGL by default to help it provide nice animations and other eye candy, so you'll want to make sure that you use {{c|eselect opengl}} to ensure that the proper OpenGL implementation for your video card is selected. If this is not done, GNOME won't start, so it's important to check this. Type {{c|eselect opengl list}} as root to list OpenGL implementations, and {{c|eselect opengl set <opengl_implementation_name>}}, again as root, to set your OpenGL implementation to the one that you deem suitable.
<!--T:20-->
Users of other graphics drivers typically don't need to perform any steps other than ensure that the correct {{c|gfxcard-}} mix-in is enabled and the system is updated (via {{c|emerge -auDN @world}} to ensure that this support is active. See the [[Install/Profiles#Graphics Settings|Graphics Settings portion of the Installation documentation]] for more information on the different mix-ins available.


{{Important|While many video drivers (those that are part of xorg-x11) do not require users to be part of the {{c|video}} group for hardware acceleration, the proprietary NVIDIA drivers definitely do require this. Please make sure that any non-root user is part of the {{c|video}} group. See {{package|x11-drivers/nvidia-drivers}} for more info on how to set up NVIDIA's proprietary drivers.}}
==== Setting up xdm (GUI log-in) ==== <!--T:21-->
 
==== Setting up xdm (GUI log-in) ====
Most users of Gnome are satisfied using {{c|gdm}}, the Gnome display manager, to log in to Gnome. To clarify: a display manager provides a graphical interface during system startup that allows users to log in to a desktop environment.  
Most users of Gnome are satisfied using {{c|gdm}}, the Gnome display manager, to log in to Gnome. To clarify: a display manager provides a graphical interface during system startup that allows users to log in to a desktop environment.  


<!--T:22-->
By default, GNOME displays the {{f|/etc/motd}} file for several seconds after you log in via GDM. The best way to eliminate this delay is to remove the unnecessary {{f|/etc/motd}} file, which only contains information related to when your stage3 was built:
By default, GNOME displays the {{f|/etc/motd}} file for several seconds after you log in via GDM. The best way to eliminate this delay is to remove the unnecessary {{f|/etc/motd}} file, which only contains information related to when your stage3 was built:
{{console|body=
{{console|body=
###i## rm /etc/motd
###i## rm /etc/motd
}}
}}
By default, after installing Gnome, GDM is not enabled. To enable GDM, edit {{f|/etc/conf.d/xdm}} and set the {{c|DISPLAYMANAGER}} variable to {{c|gdm}} instead of the default, {{c|xdm}}. When finished, your {{f|/etc/conf.d/xdm}} file should look like:
By default, after installing GNOME by hand, GDM is not enabled (it will be, however, if you used a GNOME stage3.) To enable GDM, edit {{f|/etc/conf.d/xdm}} and set the {{c|DISPLAYMANAGER}} variable to {{c|gdm}} instead of the default, {{c|xdm}}. When finished, your {{f|/etc/conf.d/xdm}} file should look like:


<!--T:23-->
{{file|name=/etc/conf.d/xdm|body=
{{file|name=/etc/conf.d/xdm|body=
# We always try and start X on a static VT. The various DMs normally default
# We always try and start X on a static VT. The various DMs normally default
Line 108: Line 124:
CHECKVT=7
CHECKVT=7


<!--T:24-->
# What display manager do you use ?
# What display manager do you use ?
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
Line 113: Line 130:
}}
}}


<!--T:25-->
Once you finish configuring that file, add the {{c|xdm}} service to the default runlevel so that GDM will start automatically when your system has finished loading other services.
Once you finish configuring that file, add the {{c|xdm}} service to the default runlevel so that GDM will start automatically when your system has finished loading other services.
{{c|xdm}} need dbus service started before. To achieve this:
{{c|xdm}} need dbus service started before. To achieve this:
Line 121: Line 139:
Above command adds dbus to list of services to be started at boot. At this point, you are encouraged to reboot your system to get system services initialized in the proper state, and to ensure that any newly-rebuilt services are running:
Above command adds dbus to list of services to be started at boot. At this point, you are encouraged to reboot your system to get system services initialized in the proper state, and to ensure that any newly-rebuilt services are running:


<!--T:26-->
{{console|body=
{{console|body=
###i## reboot
###i## reboot
}}
}}


<!--T:27-->
After the system reboots, log in and start the {{c|xdm}} service:
After the system reboots, log in and start the {{c|xdm}} service:


<!--T:28-->
{{console|body=
{{console|body=
###i## /etc/init.d/xdm start
###i## /etc/init.d/xdm start
}}
}}


<!--T:29-->
Hopefully, all goes well and you see a graphical login screen. If you would like {{c|xdm}} to start automatically at boot, you can add it to your default runlevel as follows:
Hopefully, all goes well and you see a graphical login screen. If you would like {{c|xdm}} to start automatically at boot, you can add it to your default runlevel as follows:


<!--T:30-->
{{console|body=
{{console|body=
###i## rc-update add xdm default
###i## rc-update add xdm default
}}
}}


==== Setting up xinitrc (text-based log-in) ====
==== Setting up xinitrc (text-based log-in) ==== <!--T:31-->
If, instead of using a display manager like GDM, you would rather log into the console and start Gnome from there, add the following to your {{f|~/.xinitrc}} file:
If, instead of using a display manager like GDM, you would rather log into the console and start Gnome with startx :
 
Configure openrc to autostart dbus and elogind:
{{console|body=
###i## rc-update add dbus default
###i## rc-update add elogind default
}}
 
Add the following to your {{f|~/.xinitrc}} file:
{{file|name=~/.xinitrc|body=
{{file|name=~/.xinitrc|body=
# Fix Missing Applications in Gnome
# Fix Missing Applications in Gnome
export XDG_MENU_PREFIX=gnome-
export XDG_MENU_PREFIX=gnome-


<!--T:32-->
# Properly Launch the Desired X Session
# Properly Launch the Desired X Session
exec ck-launch-session gnome-session
exec gnome-session
}}
}}
{{Note|If you need support for different input sources, there is no longer a need to configure IBus or SCIM in your {{f|~.xinitrc}} file as GNOME uses IBus natively. Simply configure it in the Gnome Control Center under the Region & Language section.}}
{{Note|If you need support for different input sources, there is no longer a need to configure IBus or SCIM in your {{f|~.xinitrc}} file as GNOME uses IBus natively. Simply configure it in the Gnome Control Center under the Region & Language section.}}


=== Upgrading from older Gnome releases ===
=== Upgrading from older Gnome releases === <!--T:33-->
To update either {{c|gnome-light}} or {{c|gnome}} to a newer version, run the following command:
To update either {{c|gnome-light}} or {{c|gnome}} to a newer version, run the following command:


<!--T:34-->
{{console|body=###i## emerge -vauDN world}}
{{console|body=###i## emerge -vauDN world}}


=== Subsystems ===
=== Subsystems === <!--T:35-->
==== Bluetooth ====
==== Bluetooth ====
For bluetooth support under Gnome, ensure that:
For bluetooth support under Gnome, ensure that:
Line 160: Line 193:
# Your user is in the {{c|plugdev}} group.
# Your user is in the {{c|plugdev}} group.


<!--T:36-->
After ensuring those two things, the {{c|bluetooth}} startup script can be added to the default runlevel and started:
After ensuring those two things, the {{c|bluetooth}} startup script can be added to the default runlevel and started:
{{console|body=
{{console|body=
Line 167: Line 201:
Once the {{c|rc}} command has been run, the {{c|bluetooth}} init file has been run, meaning that you should now be able to navigate to the Gnome Control Center's '''Bluetooth''' section to turn bluetooth on. The icon next to devices should now animate and you should be able to discover and add devices such as bluetooth keyboards and mice.
Once the {{c|rc}} command has been run, the {{c|bluetooth}} init file has been run, meaning that you should now be able to navigate to the Gnome Control Center's '''Bluetooth''' section to turn bluetooth on. The icon next to devices should now animate and you should be able to discover and add devices such as bluetooth keyboards and mice.


<!--T:37-->
{{Note|Additional kernel drivers may be necessary for certain input devices. For example, for the bluetooth Apple Magic Trackpad, the following option must be enabled in your kernel:
{{Note|Additional kernel drivers may be necessary for certain input devices. For example, for the bluetooth Apple Magic Trackpad, the following option must be enabled in your kernel:


<!--T:38-->
{{kernelop|title=Device Drivers,HID support,HID bus support,Special HID drivers|desc=
{{kernelop|title=Device Drivers,HID support,HID bus support,Special HID drivers|desc=
<M> Apple Magic Mouse/Trackpad multi-touch support
<M> Apple Magic Mouse/Trackpad multi-touch support
}}}}
}}}}


==== Printing ====
==== Printing ==== <!--T:39-->
To enable printing support, add the {{c|cupsd}} init file to the default runlevel and then start the cupsd service by running the {{c|rc}} command:
To enable printing support, add the {{c|cupsd}} init file to the default runlevel and then start the cupsd service by running the {{c|rc}} command:


<!--T:40-->
{{console|body=
{{console|body=
###i## rc-update add cupsd default
###i## rc-update add cupsd default
Line 182: Line 219:
You should now be able to navigate to the Gnome Control Center's '''Printers''' sections and add printers to your system. After adding printers to your system, you should, hopefully, be able to print to them. If you have troubles with the default printer drivers, consider reading  
You should now be able to navigate to the Gnome Control Center's '''Printers''' sections and add printers to your system. After adding printers to your system, you should, hopefully, be able to print to them. If you have troubles with the default printer drivers, consider reading  


==== Scanning ====
==== Scanning ==== <!--T:41-->


<!--T:42-->
To enable scanning support, add your user account (and the accounts of any other users who may need to scan) to the {{c|lp}} group. By adding your user account to this group, you will have access to any locally attached scanner:
To enable scanning support, add your user account (and the accounts of any other users who may need to scan) to the {{c|lp}} group. By adding your user account to this group, you will have access to any locally attached scanner:
{{console|body=###i## gpasswd -a <username> lp}}
{{console|body=###i## gpasswd -a <username> lp}}
Line 190: Line 228:
When you run {{c|xsane}}, it should be able to access your scanner.
When you run {{c|xsane}}, it should be able to access your scanner.


=== Automatically Starting Applications at Login ===
=== Automatically Starting Applications at Login === <!--T:43-->
When using an old-fashioned {{~/.xinitrc}}, loading applications when X starts is relatively easy, simply add different applications to launch on separate lines in the file. When using GDM, this can also be accomplished with ease by editing the {{f|~/.xprofile}} file. Here is a sample {{f|~/.xprofile}} that runs the {{c|xflux}} application to dim a computer's monitor at night:
When using an old-fashioned {{~/.xinitrc}}, loading applications when X starts is relatively easy, simply add different applications to launch on separate lines in the file. When using GDM, this can also be accomplished with ease by editing the {{f|~/.xprofile}} file. Here is a sample {{f|~/.xprofile}} that runs the {{c|xflux}} application to dim a computer's monitor at night:


<!--T:44-->
{{file|name=~/.xprofile|body=
{{file|name=~/.xprofile|body=
xflux -z 87107
xflux -z 87107
}}
}}


<!--T:45-->
{{Note|Remember to add an {{c|&}} at the end of any command that doesn't return directly to the shell prompt after running.}}
{{Note|Remember to add an {{c|&}} at the end of any command that doesn't return directly to the shell prompt after running.}}


=== Games ===
=== Games === <!--T:46-->
Gnome has a plethora of games that can be added to your installation of either {{c|gnome-light}} or {{c|gnome}}.  By default, the majority of Gnome games are not included in the {{c|gnome}} and {{c|gnome-light}} packages. If you are interested in playing games under Gnome, or for that matter, any other desktop environment, you will want to add your user account to the {{c|games}} group. This can be accomplished easily by running the following command:
Gnome has a plethora of games that can be added to your installation of either {{c|gnome-light}} or {{c|gnome}}.  By default, the majority of Gnome games are not included in the {{c|gnome}} and {{c|gnome-light}} packages. If you are interested in playing games under Gnome, or for that matter, any other desktop environment, you will want to add your user account to the {{c|games}} group. This can be accomplished easily by running the following command:
{{console|body=###i## gpasswd -a $USER games}}
{{console|body=###i## gpasswd -a $USER games}}
The above command appends games to the list of groups that you are already a member of. Once your user account has been added to the {{c|games}} group, you should log out and log back in to apply the changes to your user at log-in. Below is a list of games that were developed by the Gnome team with the Gnome desktop environment in mind:
The above command appends games to the list of groups that you are already a member of. Once your user account has been added to the {{c|games}} group, you should log out and log back in to apply the changes to your user at log-in. Below is a list of games that were developed by the Gnome team with the Gnome desktop environment in mind:


<!--T:47-->
*gnome-sudoku  
*gnome-sudoku  
*gnome-mastermind
*gnome-mastermind
Line 214: Line 255:
*gnome-klotski
*gnome-klotski
*gnome-tetravex
*gnome-tetravex
*gnomeboyadvance
*gnome-mud


<!--T:48-->
To install any of the above games, simply run an:
To install any of the above games, simply run an:
{{console|body=###i## emerge <gamename>}}
{{console|body=###i## emerge <gamename>}}


<!--T:49-->
[[Category:Desktop]]
[[Category:Desktop]]
[[Category:First Steps]]
[[Category:First Steps]]
[[Category:Official Documentation]]
[[Category:Official Documentation]]
</translate>

Latest revision as of 23:10, February 10, 2022

Other languages:
English • ‎español • ‎français • ‎português do Brasil • ‎中文（中国大陆）‎ • ‎한국어

GNOME 3 is an easy and elegant way to use your computer. It is designed to put you in control and bring freedom to everybody. GNOME 3 is developed by the GNOME community, a diverse, international group of contributors that is supported by an independent, non-profit foundation. GNOME

Prerequisites

Before attempting to emerge Gnome, make sure that you have installed and tested the X Window System on your computer.

Preparing to emerge

After verifying that you have installed the X Window system on your computer, change your system flavor to desktop, and enable the gnome profile mix-in. To accomplish this, run the following: 

root # epro flavor desktop
root # epro mix-ins +gnome

By enabling the gnome mix-in, various settings, including the USE portage variable, will be optimized to provide you with a relatively painless Gnome install.

Optional Wayland Support

With release-1.3, it is now possible to use Wayland instead of X as your display technology. If you would like to enable this -- it is optional -- you must also run the following command: 

root # epro mix-ins +wayland
   Warning

While wayland is supported in Funtoo, wayland itself is not considered to be mature and most people will experience better results using X rather than wayland.

When using Wayland, if you are using nvidia-drivers, you must manually enable NVIDIA's own KMS by adding the following to your params in /etc/boot.conf: nvidia-drm.modeset=1. KMS must be enabled manually when using nvidia-drivers.

X or Wayland

You will want to make sure you run etc-update or dispatch-conf to update your configuration files after everything emerges. In particular, take a look at /etc/gdm/custom.conf and ensure that the following setting is configured to match whether or not you are running Wayland. This controls whether or not gdm runs using Wayland. If gdm starts in Wayland, then it is able to launch either X or Wayland sessions. If Wayland is disabled in gdm, then it will only be able to start X sessions.

   /etc/gdm/custom.conf 
[daemon]
WaylandEnable=true

Emerging

The Funtoo Linux repositories include two ebuild "meta packages" that can be used to install Gnome. One of them, gnome-light installs a bare-bones gnome desktop with few "extra" applications and games that can be found in the gnome-extra and games-* portage categories, respectively. If you are interested in having a Gnome desktop with extra applications like a photo viewer, text editor, sound player, font viewer, etc, immediately after installing the Gnome packages, consider emerging the gnome package instead of gnome-light.

   Note

Individual Gnome applications can be installed on top of a gnome-light installation, allowing you to only install the applications you need and limit unnecessary bloat.

Below are two lists comparing some of the different packages installed by default with a gnome-light and gnome installation:

gnome-lightgnome
Includes:
  • gnome-terminal
  • nautilus (the default Gnome file manager)
  • gnome-shell (can be removed using the -gnome-shell USE flag at installation)
  • gnome-control-center
 Includes:
  • gnome-terminal
  • nautilus
  • gnome-shell
  • gnome-control-center
  • gnome-contacts
  • eog (an image viewing application)
  • gnome-weather
  • gnome-maps

... and many other applications.

Best for:
  • Users who want a smaller installation that uses less disk space
  • Users who are comfortable installing additional packages that they require when the need arises
Best for:
  • Users who want a full-featured Gnome desktop right after installation
  • Users who don't mind extra resources being used by additional applications installed on the system
How to install:

emerge gnome-light

How to install:

emerge gnome

The steps that should be followed to emerge GNOME are as follows: 

root # emerge -auDN @world
root # emerge gnome


A few finishing touches

Proprietary NVIDIA drivers

While many video drivers (those that are part of xorg-x11) do not require users to be part of the video group for hardware acceleration, the proprietary NVIDIA drivers definitely do require this. Please make sure that any non-root user is part of the video group, and ensure that Nouveau kernel modules are blacklisted. Setup steps for proprietary NVIDIA drivers can be found on the the NVIDIA Linux Display Drivers page.

Other Graphics Drivers

Users of other graphics drivers typically don't need to perform any steps other than ensure that the correct gfxcard- mix-in is enabled and the system is updated (via emerge -auDN @world to ensure that this support is active. See the Graphics Settings portion of the Installation documentation for more information on the different mix-ins available.

Setting up xdm (GUI log-in)

Most users of Gnome are satisfied using gdm, the Gnome display manager, to log in to Gnome. To clarify: a display manager provides a graphical interface during system startup that allows users to log in to a desktop environment.

By default, GNOME displays the /etc/motd file for several seconds after you log in via GDM. The best way to eliminate this delay is to remove the unnecessary /etc/motd file, which only contains information related to when your stage3 was built: 

root # rm /etc/motd

By default, after installing GNOME by hand, GDM is not enabled (it will be, however, if you used a GNOME stage3.) To enable GDM, edit /etc/conf.d/xdm and set the DISPLAYMANAGER variable to gdm instead of the default, xdm. When finished, your /etc/conf.d/xdm file should look like:

   /etc/conf.d/xdm 
# We always try and start X on a static VT. The various DMs normally default
# to using VT7. If you wish to use the xdm init script, then you should ensure
# that the VT checked is the same VT your DM wants to use. We do this check to
# ensure that you haven't accidentally configured something to run on the VT
# in your /etc/inittab file so that you don't get a dead keyboard.
CHECKVT=7

# What display manager do you use ?
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
DISPLAYMANAGER="gdm"

Once you finish configuring that file, add the xdm service to the default runlevel so that GDM will start automatically when your system has finished loading other services. xdm need dbus service started before. To achieve this: 

root # rc-update add dbus default
root # rc-update add elogind default

Above command adds dbus to list of services to be started at boot. At this point, you are encouraged to reboot your system to get system services initialized in the proper state, and to ensure that any newly-rebuilt services are running: 

root # reboot

After the system reboots, log in and start the xdm service: 

root # /etc/init.d/xdm start

Hopefully, all goes well and you see a graphical login screen. If you would like xdm to start automatically at boot, you can add it to your default runlevel as follows: 

root # rc-update add xdm default

Setting up xinitrc (text-based log-in)

If, instead of using a display manager like GDM, you would rather log into the console and start Gnome with startx :

Configure openrc to autostart dbus and elogind: 

root # rc-update add dbus default
root # rc-update add elogind default

Add the following to your ~/.xinitrc file:

   ~/.xinitrc 
# Fix Missing Applications in Gnome
export XDG_MENU_PREFIX=gnome-

# Properly Launch the Desired X Session
exec gnome-session
   Note

If you need support for different input sources, there is no longer a need to configure IBus or SCIM in your ~.xinitrc file as GNOME uses IBus natively. Simply configure it in the Gnome Control Center under the Region & Language section.

Upgrading from older Gnome releases

To update either gnome-light or gnome to a newer version, run the following command: 

root # emerge -vauDN world

Subsystems

Bluetooth

For bluetooth support under Gnome, ensure that:

  1. Bluetooth support is enabled within your kernel (using modules is fine).
  2. Your bluetooth hardware is turned on.
  3. Your user is in the plugdev group.

After ensuring those two things, the bluetooth startup script can be added to the default runlevel and started: 

root # rc-update add bluetooth default
root # rc

Once the rc command has been run, the bluetooth init file has been run, meaning that you should now be able to navigate to the Gnome Control Center's Bluetooth section to turn bluetooth on. The icon next to devices should now animate and you should be able to discover and add devices such as bluetooth keyboards and mice.

   Note

Additional kernel drivers may be necessary for certain input devices. For example, for the bluetooth Apple Magic Trackpad, the following option must be enabled in your kernel:

Under Device Drivers-->HID support-->HID bus support-->Special HID drivers:

<M> Apple Magic Mouse/Trackpad multi-touch support

Printing

To enable printing support, add the cupsd init file to the default runlevel and then start the cupsd service by running the rc command: 

root # rc-update add cupsd default
root # rc

You should now be able to navigate to the Gnome Control Center's Printers sections and add printers to your system. After adding printers to your system, you should, hopefully, be able to print to them. If you have troubles with the default printer drivers, consider reading

Scanning

To enable scanning support, add your user account (and the accounts of any other users who may need to scan) to the lp group. By adding your user account to this group, you will have access to any locally attached scanner: 

root # gpasswd -a <username> lp

After adding yourself and any other desired users to the lp local printing group, install xsane, a graphical scanning frontend, by running the following command: 

root # emerge xsane

When you run xsane, it should be able to access your scanner.

Automatically Starting Applications at Login

When using an old-fashioned Template:~/.xinitrc, loading applications when X starts is relatively easy, simply add different applications to launch on separate lines in the file. When using GDM, this can also be accomplished with ease by editing the ~/.xprofile file. Here is a sample ~/.xprofile that runs the xflux application to dim a computer's monitor at night:

   ~/.xprofile 
xflux -z 87107
   Note

Remember to add an & at the end of any command that doesn't return directly to the shell prompt after running.

Games

Gnome has a plethora of games that can be added to your installation of either gnome-light or gnome. By default, the majority of Gnome games are not included in the gnome and gnome-light packages. If you are interested in playing games under Gnome, or for that matter, any other desktop environment, you will want to add your user account to the games group. This can be accomplished easily by running the following command: 

root # gpasswd -a $USER games

The above command appends games to the list of groups that you are already a member of. Once your user account has been added to the games group, you should log out and log back in to apply the changes to your user at log-in. Below is a list of games that were developed by the Gnome team with the Gnome desktop environment in mind:

  • gnome-sudoku
  • gnome-mastermind
  • gnome-nibbles
  • gnome-robots
  • gnome-chess
  • gnome-hearts
  • gnome-mahjongg
  • gnome-mines
  • gnome-klotski
  • gnome-tetravex

To install any of the above games, simply run an: 

root # emerge <gamename>
Retrieved from "https://www.funtoo.org/index.php?title=GNOME_First_Steps&oldid=38870"