GNOME (Español)

From ArchWiki
Revision as of 03:30, 12 April 2011 by Sironitomas (Talk | contribs) (Created page with "{{i18n|GNOME 3}} Category:Desktop environments (Español) Category:HOWTOs (Español) {{Article summary start}} {{Article summary text|GNOME 3 provee un escritorio moder...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Template:Article summary start

Template:Article summary text Template:Article summary heading Template:Article summary text Template:Article summary end

Para GNOME 3, el Proyecto GNOME ha empezado desde base y ha creado un escritorio moderno, completamente nuevo diseñado para las tecnologías de los usuarios de hoy. En GNOME 3:

  • Hay fuente y tema visual nuevo y moderno por defecto
  • La vista de actividades que provee una forma facil de acceder a todas tus ventanas y aplicaciones
  • Servicios de mensajería de escritorio integrados
  • Paneles de sistema y notificaciones mas discretos y eficientes
  • Característica de búsqueda rápida de Actividades.
  • Una nueva aplicación de Configuración del Sistema

[mas detalles en el sitio GNOME3]


GNOME3 comes with two interfaces, gnome-shell (the new, standard layout) and fallback mode. gnome-session will automatically detect if your computer is capable to run gnome-shell and it would start the fallback mode if not.

Fallback mode is very much alike the GNOME 2.x layout (while using gnome-panel and metacity, instead of gnome-shell and Mutter).

If you are on fallback mode you can still change the window manager with your preferred one.

Upgrade from the current gnome 2.32

Enable testing repo.

Edit /etc/pacman.conf and uncomment testing.

Warning: It's very important for the new repo to be on the top, otherwise pacman will not upgrade GNOME
 #testing uncommented
Include = /etc/pacman.d/mirrorlist

Warning: The session might crash during update and is recommended running the update command in a screen session, from another DE or WM or from tty
# pacman -Syu 

Important: You will end up with a system that has GNOME 3.x fallback mode. To install the new shell:

# pacman -S gnome-shell

Installing to a new system

Enable testing in the same way as above.

# pacman -Syu testing/gnome

Para aplicaciones adicionales

# pacman -Syu testing/gnome-extra

Modulos y demonios que GNOME necesita

El escritorio GNOME requiere un demonio, DBUS para una operacion correcta

Para iniciar el demonio DBUS

# /etc/rc.d/dbus start

O agrega estos demonios a el arreglo DAEMONS en Template:Filename asi estos inician de forma automatica en el arranque.

DAEMONS=(syslog-ng dbus network crond)

GVFS allows the mounting of virtual file systems (e.g. file systems over FTP or SMB) to be used by other applications, including the GNOME file manager Nautilus. This is done with the use of FUSE: a user space virtual file system layer kernel module.

To load the FUSE kernel module:

# modprobe fuse

Or add the module to the MODULES array in Template:Filename so they will load at boot up, e.g.:

MODULES=(fuse usblp)
Note: FUSE is a kernel module, not a daemon.

Running GNOME

For a better desktop integration is recommended GDM.

# pacman -S gdm

Check out Display_Manager to learn how to start it correctly.

If you prefer to start it from console, add the following line to your Template:Filename file, making sure it's the last line and the only one that starts with exec (see xinitrc):

exec ck-launch-session gnome-session

Now GNOME will start when you enter the following command:

$ startx

Using the shell



Using Gnome-tweak-tool

# pacman -S gnome-tweak-tool

This tool can customize fonts, themes and some other useful settings like action when lid is closed.

A good customization tutorial is which explores the power of gsettings

Changing the GTK3 theme using settings.ini

Similar to Template:Filename for GTK2+ it is possible to set the GTK3 (Gnome 3) theme via Template:Filename. By default Template:Filename is interpreted as Template:Filename.


 gtk-theme-name = Adwaita
 gtk-fallback-icon-theme = gnome

It may be necessary to restart one's DE or WM for the settings to be applied.

Solution for missing "Startup Programs" tool

You can use .config dir in your home directory to create a autostart folder.

$ mkdir ~/.config/autostart

And inside put your programm.desktop files with the following scheme inside: (example program is empathy ~/.config/autostart/empathy.desktop)

 [Desktop Entry]
 Name=Empathy messaging

Next time you log in to gnome3 program will starts automatic.

Enabling fallback mode

Your session would start automatically to fallback mode if gnome-shell is not present. If you want to enable it while having gnome-shell installed, open gnome-control-center. Open System Info > Graphics. Change Forced Fallback Mode to ON.

Enabling hidden features

Gnome 3.0 hides a lot of useful options and you have to use dconf-editor to customize them.

How to shutdown through the Status menu

For now, the Shutdown option seems to be hidden if the user presses the Status menu on the upper right. If you want to shutdown your system through the Status menu, click on it and then press the Alt button. The "Suspend" option will instantly turn into "Power off...", as long as you press the Alt button, which will allow you to properly shutdown your system.

Enabling integrated messaging

Empathy, the engine behind the integrated messaging, and all of the system settings based on your messaging accounts will not show up unless the telepathy group of packages or at least one of the backends (telepathy-gabble, or telepathy-haze, for example) is installed. These are not included in the default Arch GNOME installs and the Empathy interface doesn't give a nice error message, it just fails to work silently. You can install them:

# pacman -S telepathy

Enabling extensions

Gnome Shell can be customised to an extent with extensions that have been written by others. These provide functionality like having a dock that is always present, and being able to change the shell theme. More details on the functionality of currently available extensions is given here You can use the gnome-shell-extensions-git package in the AUR to install them. Restart Gnome to enable them.

If installing the extensions causes Gnome to stop working then you must remove the user-theme extension and and the auto-move-windows extension from their installation directory (could be in ~/.local/share/gnome-shell/extensions or /usr/share/gnome-shell/extensions or /usr/local/share/gnome-shell/extensions). Removing or adding extensions to these directories will remove or install them form the system. More details on Gnome Shell extensions are available here.


My GTK2+ apps show segfaults and won't start

That usually happens when oxygen-gtk is installed. That theme conflicts somehow with GNOME 3's or/and GTK3 settings and when it has been set as a GTK2 theme, the GTK2 apps segfault with errors like:

 (firefox-bin:14345): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(firefox-bin:14345): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(firefox-bin:14345): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion `GDK_IS_SCREEN (screen)' failed

(firefox-bin:14345): Gdk-CRITICAL **: IA__gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed

(firefox-bin:14345): Gdk-CRITICAL **: IA__gdk_screen_get_default_colormap: assertion `GDK_IS_SCREEN (screen)' failed

(firefox-bin:14345): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion `GDK_IS_SCREEN (screen)' failed

(firefox-bin:14345): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion `GDK_IS_SCREEN (screen)' failed

(firefox-bin:14345): Gdk-CRITICAL **: IA__gdk_window_new: assertion `GDK_IS_WINDOW (parent)' failed
Segmentation fault

The current "workaround" is to remove oxygen-gtk from the system completely and set another theme for your apps.