- Timestamp:
- 02/22/2023 08:51:43 PM (19 months ago)
- Branches:
- 11.3, 12.0, 12.1, 12.2, gimp3, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/for-12.3, xry111/llvm18, xry111/spidermonkey128, xry111/xf86-video-removal
- Children:
- 12fe806, 1ae85c65
- Parents:
- e461d1a
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
gnome/platform/gnome-session.xml
re461d1a ra875313 168 168 href="../../xincludes/meson-buildtype-release.xml"/> 169 169 </sect2> 170 171 <sect2 role="starting"> 172 <title>Starting GNOME</title> 173 174 <para> 175 The easiest way to start GNOME is to use a display manager. 176 <xref linkend="gdm"/> is the recommendend display manager. 177 </para> 178 179 <para> 180 It is also possible to start <application>GNOME</application> from the 181 command line. However, you must still have <xref linkend="gdm"/> installed 182 for some portions of the desktop to work. One reason to start from the 183 command line is if you want Wayland support on a system that has the 184 proprietary NVIDIA driver installed, since GDM will not show the Wayland 185 session type on such a system. 186 </para> 187 188 <para> 189 To start <application>GNOME</application> using 190 <xref role="nodep" linkend="xinit"/>, run the following commands: 191 </para> 192 193 <screen role="nodump"><userinput>cat > ~/.xinitrc << "EOF" 194 <literal>dbus-run-session gnome-session</literal> 195 EOF 196 197 startx</userinput></screen> 198 199 <para> 200 Alternatively, to start <application>GNOME</application> with Wayland 201 support, run the following command: 202 </para> 203 204 <screen role="nodump"><userinput>XDG_SESSION_TYPE=wayland dbus-run-session gnome-session</userinput></screen> 205 206 </sect2> 170 207 171 208 <sect2 role="content">
Note:
See TracChangeset
for help on using the changeset viewer.