1 |
pacho 10/05/02 11:04:09 |
2 |
|
3 |
Modified: gnome-2.28-upgrade.xml |
4 |
Log: |
5 |
Better wording following David Abbott suggestions. |
6 |
|
7 |
Revision Changes Path |
8 |
1.3 xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.28-upgrade.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.28-upgrade.xml?rev=1.3&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.28-upgrade.xml?rev=1.3&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.28-upgrade.xml?r1=1.2&r2=1.3 |
13 |
|
14 |
Index: gnome-2.28-upgrade.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.28-upgrade.xml,v |
17 |
retrieving revision 1.2 |
18 |
retrieving revision 1.3 |
19 |
diff -u -r1.2 -r1.3 |
20 |
--- gnome-2.28-upgrade.xml 17 Apr 2010 13:46:12 -0000 1.2 |
21 |
+++ gnome-2.28-upgrade.xml 2 May 2010 11:04:09 -0000 1.3 |
22 |
@@ -1,6 +1,6 @@ |
23 |
<?xml version="1.0" encoding="UTF-8"?> |
24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.28-upgrade.xml,v 1.2 2010/04/17 13:46:12 pacho Exp $ --> |
26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/gnome/howtos/gnome-2.28-upgrade.xml,v 1.3 2010/05/02 11:04:09 pacho Exp $ --> |
27 |
|
28 |
<guide link="/proj/en/desktop/gnome/howtos/gnome-2.28-upgrade.xml"> |
29 |
<title>Gnome 2.28 Upgrade Guide</title> |
30 |
@@ -17,24 +17,23 @@ |
31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
32 |
<license/> |
33 |
|
34 |
-<version>1.0</version> |
35 |
-<date>2010-03-30</date> |
36 |
+<version>1.1</version> |
37 |
+<date>2010-05-02</date> |
38 |
|
39 |
<chapter> |
40 |
<title>Changes</title> |
41 |
|
42 |
<section> |
43 |
<body> |
44 |
-<note>You can select <b>gnome</b> subprofile to automatically enable most |
45 |
-USE flags needed by <c>gnome-base/gnome</c> and, then, not needing to care |
46 |
-about missing USE flags being enabled. Please follow <uri link="http://www.gentoo.org/doc/en/gentoo-upgrading.xml#doc_chap3">these instructions</uri> |
47 |
+<note>You can select the <b>gnome</b> subprofile to automatically enable most |
48 |
+USE flags needed by <c>gnome-base/gnome</c>. Please follow <uri link="http://www.gentoo.org/doc/en/gentoo-upgrading.xml#doc_chap3">these instructions</uri> |
49 |
to select this profile if desired.</note> |
50 |
</body> |
51 |
</section> |
52 |
|
53 |
<section> |
54 |
<body> |
55 |
-<note>When running <c>gconftool-2</c> to change settings, remember that you |
56 |
+<note>When running <c>gconftool-2</c> to change settings, you |
57 |
can run it as root appending <c>--config-source |
58 |
xml:readwrite:/etc/gconf/gconf.xml.defaults</c> to the end of the command to |
59 |
set default preferences for <b>all</b> users. |
60 |
@@ -43,12 +42,12 @@ |
61 |
</section> |
62 |
|
63 |
<section> |
64 |
-<title>Drives automounting</title> |
65 |
+<title>Drives auto-mounting</title> |
66 |
<body> |
67 |
|
68 |
<p> |
69 |
<c>sys-apps/gnome-disk-utility</c> support in <c>gnome-base/gvfs</c> is now required |
70 |
-by nautilus to automount drives. Because of this, you need to be sure gvfs is built |
71 |
+by nautilus to auto-mount drives. Because of this, you need to be sure gvfs is built |
72 |
with <c>gdu</c> USE flag enabled. |
73 |
</p> |
74 |
|
75 |
@@ -70,7 +69,7 @@ |
76 |
<p> |
77 |
A dependency on <c>gnome-extra/polkit-gnome</c> has been added to <c>gnome-base/gnome</c> |
78 |
meta ebuild to be sure users who enable <c>policykit</c> USE flag get information when they |
79 |
-do not have the correct priviledges. |
80 |
+do not have the correct privileges. |
81 |
</p> |
82 |
|
83 |
</body> |
84 |
@@ -126,9 +125,9 @@ |
85 |
<body> |
86 |
|
87 |
<p> |
88 |
-Due <c>sys-apps/hal</c> deprecation, upstream decided to drop its support causing |
89 |
+Due to <c>sys-apps/hal</c> deprecation, upstream decided to drop its support causing |
90 |
synaptics hal settings to be ignored. As a workaround until migration away |
91 |
-from hal ends,you can try to configure your touchpad using the settings tool in |
92 |
+from hal ends, you can try to configure your touchpad using the settings tool in |
93 |
<c>System->Preferences->Mouse->Touchpad</c>, |
94 |
but it will not allow you to define some settings like touchpad size, tap zones, tap sensitivity, etc. |
95 |
</p> |
96 |
@@ -186,7 +185,7 @@ |
97 |
</p> |
98 |
|
99 |
<p> |
100 |
-You can, anyway, try to install newer epiphany and epiphany-extensions simply following |
101 |
+You can install newer epiphany and epiphany-extensions simply following |
102 |
<uri |
103 |
link="http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=3#doc_chap2">handbook |
104 |
instructions</uri> to install testing packages on a stable system. |
105 |
@@ -199,16 +198,21 @@ |
106 |
<title>Gvfs problems while upgrading</title> |
107 |
<body> |
108 |
|
109 |
+<impo> |
110 |
+Be sure to restart gvfs at the end of the update is needed to avoid weird |
111 |
+errors. |
112 |
+</impo> |
113 |
+ |
114 |
<p> |
115 |
-Restarting gvfs at the end of the update is needed to avoid weird errors. The safest way to restart |
116 |
-it is to log off/on again because doing it on a logged in session could cause crashing problems. |
117 |
+The safest way to restart it is to log off/on again because doing it on a |
118 |
+logged in session could cause crashing problems. |
119 |
</p> |
120 |
|
121 |
</body> |
122 |
</section> |
123 |
|
124 |
<section> |
125 |
-<title>Cannot click on Flash elements and other problems related with mouse interaction</title> |
126 |
+<title>Can not click on Flash elements and other problems related with mouse interaction</title> |
127 |
<body> |
128 |
|
129 |
<p> |
130 |
@@ -220,8 +224,8 @@ |
131 |
</p> |
132 |
|
133 |
<p> |
134 |
-On the other hand, this change can cause problems on applications still not prepared to use it like |
135 |
-flashplayer or vmware-workstation. For workarounding these issues, you simply need to launch the app |
136 |
+On the other hand, this change can cause problems with applications still not prepared to use it like |
137 |
+flashplayer or vmware-workstation. To workaround these issues, you simply need to launch the app |
138 |
running <c>GDK_NATIVE_WINDOWS=1 application</c> like, for example, <c>GDK_NATIVE_WINDOWS=1 firefox</c>, |
139 |
getting flashplayer working ok again since that variable turns off this new feature. |
140 |
</p> |