From: "JosA MarAa Alonso (nimiux)" <nimiux@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/es/desktop/gnome/howtos: gnome-3.2-upgrade.xml
Date: Mon, 28 Nov 2011 20:36:03 +0000 (UTC) [thread overview]
Message-ID: <20111128203603.264E92004B@flycatcher.gentoo.org> (raw)
nimiux 11/11/28 20:36:03
Modified: gnome-3.2-upgrade.xml
Log:
Document the fact that "Zaphod mode" dualhead is incompatible with gnome-shell.
Revision Changes Path
1.4 xml/htdocs/proj/es/desktop/gnome/howtos/gnome-3.2-upgrade.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/es/desktop/gnome/howtos/gnome-3.2-upgrade.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/es/desktop/gnome/howtos/gnome-3.2-upgrade.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/es/desktop/gnome/howtos/gnome-3.2-upgrade.xml?r1=1.3&r2=1.4
Index: gnome-3.2-upgrade.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/es/desktop/gnome/howtos/gnome-3.2-upgrade.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- gnome-3.2-upgrade.xml 27 Nov 2011 19:32:01 -0000 1.3
+++ gnome-3.2-upgrade.xml 28 Nov 2011 20:36:03 -0000 1.4
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/es/desktop/gnome/howtos/gnome-3.2-upgrade.xml,v 1.3 2011/11/27 19:32:01 nimiux Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/es/desktop/gnome/howtos/gnome-3.2-upgrade.xml,v 1.4 2011/11/28 20:36:03 nimiux Exp $ -->
<guide lang="es">
<title>Guía de actualización a GNOME 3.2</title>
@@ -21,8 +21,8 @@
<!-- Vea http://creativecommons.org/licenses/by-sa/2.5/deed.es -->
<license/>
-<version>0.2.4</version>
-<date>2011-11-27</date>
+<version>0.2.5</version>
+<date>2011-11-28</date>
<chapter>
<title>Cambios</title>
@@ -449,6 +449,23 @@
</body>
</section>
+
+<section>
+<title>Configuraciones con doble monitor</title>
+
+<body>
+<p>
+Tal y como se informa en la <uri
+link="https://bugs.gentoo.org/show_bug.cgi?id=392013">incidencia 392013
+</uri>, La interfaz de GNOME no arrancará correctamente con configuraciones
+de doble monitor "modo Zaphod mode" (esto es, las configuraciones con
+varias secciones <e>Device</e> en <path>xorg.conf</path>). Si está
+utilzando esta configuración de doble monitor, únicamente podrá trabajar
+en modo alternativo.
+</p>
+
+</body>
+</section>
</chapter>
<chapter>
next reply other threads:[~2011-11-28 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 20:36 JosA MarAa Alonso (nimiux) [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-15 22:03 [gentoo-commits] gentoo commit in xml/htdocs/proj/es/desktop/gnome/howtos: gnome-3.2-upgrade.xml JosA MarAa Alonso (nimiux)
2012-01-03 16:32 JosA MarAa Alonso (nimiux)
2011-12-12 21:53 JosA MarAa Alonso (nimiux)
2011-12-09 19:05 JosA MarAa Alonso (nimiux)
2011-12-09 18:54 JosA MarAa Alonso (nimiux)
2011-12-09 18:50 JosA MarAa Alonso (nimiux)
2011-11-28 20:39 JosA MarAa Alonso (nimiux)
2011-11-27 19:32 JosA MarAa Alonso (nimiux)
2011-11-27 19:29 JosA MarAa Alonso (nimiux)
2011-11-26 20:10 JosA MarAa Alonso (nimiux)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111128203603.264E92004B@flycatcher.gentoo.org \
--to=nimiux@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox