~ubuntu-branches/ubuntu/natty/gdm/natty-updates : revision 241

1

# Slovenian translation for gdm.

2

3

# This file is distributed under the same license as the gdm package.

4

#

5

# Ime Priimek <email>, leto

6

#

7

msgid ""

8

msgstr ""

9

"Project-Id-Version: gdm help master\n"

10

"POT-Creation-Date: 2010-10-16 18:19+0000\n"

11

"PO-Revision-Date: 2010-10-17 21:12+0100\n"

12

"Last-Translator: Matej Urbančič <mateju@svn.gnome.org>\n"

13

"Language-Team: Slovenian GNOME Translation Team <gnome-si@googlegroups.com>\n"

14

"Language: \n"

15

"MIME-Version: 1.0\n"

16

"Content-Type: text/plain; charset=UTF-8\n"

17

"Content-Transfer-Encoding: 8bit\n"

18

"Plural-Forms: nplurals=4; plural=(n%100==1 ? 1 : n%100==2 ? 2 : n%100==3 || n%100==4 ? 3 : 0);\n"

19

"X-Poedit-Country: SLOVENIA\n"

20

"X-Poedit-Language: Slovenian\n"

21

"X-Poedit-SourceCharset: utf-8\n"

22

23

#: C/gdm.xml:13(title)

24

msgid "GNOME Display Manager Reference Manual"

25

msgstr ""

26

27

#: C/gdm.xml:17(revnumber)

28

msgid "0.0"

29

msgstr "0.0"

30

31

#: C/gdm.xml:18(date)

32

msgid "2008-09"

33

msgstr "2008-09"

34

35

#: C/gdm.xml:23(para)

36

msgid "GDM is the GNOME Display Manager, a graphical login program."

37

msgstr ""

38

39

#: C/gdm.xml:30(firstname)

40

msgid "Martin"

41

msgstr "Martin"

42

43

#: C/gdm.xml:30(othername)

44

msgid "K."

45

msgstr "K."

46

47

#: C/gdm.xml:31(surname)

48

msgid "Petersen"

49

msgstr "Petersen"

50

51

#: C/gdm.xml:33(email)

52

msgid "mkp@mkp.net"

53

msgstr "mkp@mkp.net"

54

55

#: C/gdm.xml:37(firstname)

56

msgid "George"

57

msgstr "George"

58

59

#: C/gdm.xml:37(surname)

60

msgid "Lebl"

61

msgstr "Lebl"

62

63

#: C/gdm.xml:39(email)

64

msgid "jirka@5z.com"

65

msgstr "jirka@5z.com"

66

67

#: C/gdm.xml:43(firstname)

68

msgid "Jon"

69

msgstr "Jon"

70

71

#: C/gdm.xml:43(surname)

72

msgid "McCann"

73

msgstr "McCann"

74

75

#: C/gdm.xml:45(email)

76

msgid "mccann@jhu.edu"

77

msgstr "mccann@jhu.edu"

78

79

#: C/gdm.xml:49(firstname)

80

msgid "Ray"

81

msgstr "Ray"

82

83

#: C/gdm.xml:49(surname)

84

msgid "Strode"

85

msgstr "Strode"

86

87

#: C/gdm.xml:51(email)

88

msgid "rstrode@redhat.com"

89

msgstr "rstrode@redhat.com"

90

91

#: C/gdm.xml:55(firstname)

92

msgid "Brian"

93

msgstr "Brian"

94

95

#: C/gdm.xml:55(surname)

96

msgid "Cameron"

97

msgstr "Cameron"

98

99

#: C/gdm.xml:57(email)

100

msgid "Brian.Cameron@Sun.COM"

101

msgstr "brian.cameron@sun.com"

102

103

#: C/gdm.xml:62(year)

104

msgid "1998"

105

msgstr "1998"

106

107

#: C/gdm.xml:63(year)

108

msgid "1999"

109

msgstr "1999"

110

111

#: C/gdm.xml:64(holder)

112

msgid "Martin K. Petersen"

113

msgstr "Martin K. Petersen"

114

115

#: C/gdm.xml:67(year)

116

msgid "2001"

117

msgstr "2001"

118

119

#: C/gdm.xml:68(year)

120

#: C/gdm.xml:73(year)

121

#: C/gdm.xml:79(year)

122

msgid "2003"

123

msgstr "2003"

124

125

#: C/gdm.xml:69(year)

126

#: C/gdm.xml:80(year)

127

msgid "2004"

128

msgstr "2004"

129

130

#: C/gdm.xml:70(holder)

131

msgid "George Lebl"

132

msgstr "George Lebl"

133

134

#: C/gdm.xml:74(year)

135

#: C/gdm.xml:83(year)

136

msgid "2007"

137

msgstr "2007"

138

139

#: C/gdm.xml:75(year)

140

#: C/gdm.xml:84(year)

141

msgid "2008"

142

msgstr "2008"

143

144

#: C/gdm.xml:76(holder)

145

msgid "Red Hat, Inc."

146

msgstr "Red Hat, Inc."

147

148

#: C/gdm.xml:81(year)

149

msgid "2005"

150

msgstr "2005"

151

152

#: C/gdm.xml:82(year)

153

msgid "2006"

154

msgstr "2006"

155

156

#: C/gdm.xml:85(holder)

157

msgid "Sun Microsystems, Inc."

158

msgstr "Sun Microsystems, Inc."

159

160

#: C/gdm.xml:2(para)

161

msgid "Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy of the GFDL at this <ulink type=\"help\" url=\"ghelp:fdl\">link</ulink> or in the file COPYING-DOCS distributed with this manual."

162

msgstr ""

163

164

#: C/gdm.xml:12(para)

165

msgid "This manual is part of a collection of GNOME manuals distributed under the GFDL. If you want to distribute this manual separately from the collection, you can do so by adding a copy of the license to the manual, as described in section 6 of the license."

166

msgstr ""

167

168

#: C/gdm.xml:19(para)

169

msgid "Many of the names used by companies to distinguish their products and services are claimed as trademarks. Where those names appear in any GNOME documentation, and the members of the GNOME Documentation Project are made aware of those trademarks, then the names are in capital letters or initial capital letters."

170

msgstr ""

171

172

#: C/gdm.xml:35(para)

173

msgid "DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"

174

msgstr ""

175

176

#: C/gdm.xml:55(para)

177

msgid "UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES."

178

msgstr ""

179

180

#: C/gdm.xml:28(para)

181

msgid "DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: <placeholder-1/>"

182

msgstr ""

183

184

#: C/gdm.xml:90(releaseinfo)

185

#: C/gdm.xml:101(para)

186

msgid "This manual describes version 2.26.0 of the GNOME Display Manager. It was last updated on 02/10/2009."

187

msgstr ""

188

189

#: C/gdm.xml:99(title)

190

msgid "Terms and Conventions Used in This Manual"

191

msgstr ""

192

193

#: C/gdm.xml:106(para)

194

msgid "Chooser - A program used to select a remote host for managing a display remotely on the attached display (<command>gdm-host-chooser</command>)."

195

msgstr ""

196

197

#: C/gdm.xml:111(para)

198

msgid "FreeDesktop - The organization providing desktop standards, such as the Desktop Entry Specification used by GDM. <ulink type=\"http\" url=\"http://www.freedesktop.org/\"> http://www.freedesktop.org</ulink>."

199

msgstr ""

200

201

#: C/gdm.xml:117(para)

202

msgid "GDM - GNOME Display Manager. Used to describe the software package as a whole."

203

msgstr ""

204

205

#: C/gdm.xml:122(para)

206

msgid "Greeter - The graphical login window (<command>gdm-simple-greeter</command>)."

207

msgstr ""

208

209

#: C/gdm.xml:126(para)

210

msgid "PAM - Pluggable Authentication Mechanism"

211

msgstr ""

212

213

#: C/gdm.xml:130(para)

214

msgid "XDMCP - X Display Manage Protocol"

215

msgstr ""

216

217

#: C/gdm.xml:134(para)

218

msgid "Xserver - An implementation of the X Window System. For example the Xorg Xserver provided by the X.org Foundation <ulink type=\"http\" url=\"http://www.x.org/\">http://www.x.org</ulink>."

219

msgstr ""

220

221

#: C/gdm.xml:140(para)

222

msgid "Paths that start with a word in angle brackets are relative to the installation prefix. I.e. <filename><share>/pixmaps/</filename> refers to <filename>/usr/share/pixmaps</filename> if GDM was configured with <command>--prefix=/usr</command>."

223

msgstr ""

224

225

#: C/gdm.xml:151(title)

226

msgid "Overview"

227

msgstr "Pregled"

228

229

#: C/gdm.xml:154(title)

230

msgid "Introduction"

231

msgstr "Uvod"

232

233

#: C/gdm.xml:156(para)

234

msgid "The GNOME Display Manager (GDM) is a display manager that implements all significant features required for managing attached and remote displays. GDM was written from scratch and does not contain any XDM or X Consortium code."

235

msgstr ""

236

237

#: C/gdm.xml:163(para)

238

msgid "Note that GDM is configurable, and many configuration settings have an impact on security. Issues to be aware of are highlighted in this document."

239

msgstr ""

240

241

#: C/gdm.xml:169(para)

242

msgid "Please note that some Operating Systems configure GDM to behave differently than the default values as described in this document. If GDM does not seem to behave as documented, then check to see if any related configuration may be different than described here."

243

msgstr ""

244

245

#: C/gdm.xml:176(para)

246

msgid "For further information about GDM, refer to the project website at <ulink type=\"http\" url=\"http://www.gnome.org/projects/gdm/\"> http://www.gnome.org/projects/gdm</ulink> and the project Wiki <ulink type=\"http\" url=\"http://live.gnome.org/GDM\"> http://live.gnome.org/GDM</ulink>."

247

msgstr ""

248

249

#: C/gdm.xml:184(para)

250

msgid "For discussion or queries about GDM, refer to the <address><email>gdm-list@gnome.org</email></address> mail list. This list is archived, and is a good resource to check to seek answers to common questions. This list is archived at <ulink type=\"http\" url=\"http://mail.gnome.org/archives/gdm-list/\"> http://mail.gnome.org/archives/gdm-list/</ulink> and has a search facility to look for messages with keywords."

251

msgstr ""

252

253

#: C/gdm.xml:194(para)

254

msgid "Please submit any bug reports or enhancement requests to the \"gdm\" category in <ulink type=\"http\" url=\"http://bugzilla.gnome.org/\"> http://bugzilla.gnome.org</ulink>."

255

msgstr ""

256

257

#: C/gdm.xml:203(title)

258

msgid "Interface Stability"

259

msgstr ""

260

261

#: C/gdm.xml:205(para)

262

msgid "GDM 2.20 and earlier supported stable configuration interfaces. However, the codebase was completely rewritten for GDM 2.22, and is not completely backward compatible with older releases. This is in part because things work differently, so some options just don't make sense, in part because some options never made sense, and in part because some functionality has not been reimplemented yet."

263

msgstr ""

264

265

#: C/gdm.xml:214(para)

266

msgid "Interfaces which continue to be supported in a stable fashion include the Init, PreSession, PostSession, PostLogin, and Xsession scripts. Some daemon configuration options in the <filename><etc>/gdm/custom.conf</filename> file continue to be supported. Also, the <filename>~/.dmrc</filename>, and face browser image locations are still supported."

267

msgstr ""

268

269

#: C/gdm.xml:223(para)

270

msgid "GDM 2.20 and earlier supported the ability to manage multiple displays with separate graphics cards, such as used in terminal server environments, login in a window via a program like Xnest or Xephyr, the gdmsetup program, XML-based greeter themes, and the ability to run the XDMCP chooser from the login screen. These features were not added back during the 2.22 rewrite."

271

msgstr ""

272

273

#: C/gdm.xml:235(title)

274

msgid "Functional Description"

275

msgstr ""

276

277

#. <para>

278

#. TODO - Would be good to discuss D-Bus, perhaps the new GObject model,

279

#. and to explain the reasons why the rewrite made GDM better.

280

#. From a high-level overview perspective, rather than the

281

#. technical aspects.

282

#. </para>

283

#: C/gdm.xml:246(para)

284

msgid "GDM is responsible for managing displays on the system. This includes authenticating users, starting the user session, and terminating the user session. GDM is configurable and the ways it can be configured are described in the \"Configuring GDM\" section of this document. GDM is also accessible for users with disabilities."

285

msgstr ""

286

287

#: C/gdm.xml:254(para)

288

msgid "GDM provides the ability to manage the main console display, and displays launched via VT. It is integrated with other programs, such as the Fast User Switch Applet (FUSA) and gnome-screensaver to manage multiple displays on the console via the Xserver Virtual Terminal (VT) interface. It also can manage XDMCP displays."

289

msgstr ""

290

291

#: C/gdm.xml:262(para)

292

msgid "Regardless of the display type, GDM will do the following when it manages the display. It will start an Xserver process, then run the <filename>Init</filename> script as the root user, and start the greeter program on the display."

293

msgstr ""

294

295

#: C/gdm.xml:269(para)

296

msgid "The greeter program is run as the unprivileged \"gdm\" user/group. This user and group are described in the \"Security\" section of this document. The main function of the greeter program is to authenticate the user. The authentication process is driven by Pluggable Authentication Modules (PAM). The PAM modules determine what prompts (if any) are shown to the user to authenticate. On the average system, the greeter program will request a username and password for authentication. However some systems may be configured to use alternative mechanisms such as a fingerprint or SmartCard reader. GDM and PAM can be configured to not require any input, which will cause GDM to automatically log in and simply start a session, which can be useful for some environments, such as for kiosks."

297

msgstr ""

298

299

#: C/gdm.xml:285(para)

300

msgid "In addition to authentication, the greeter program allows the user to select which session to start and which language to use. Sessions are defined by files that end in the .desktop suffix and more information about these files can be found in the \"GDM User Session and Language Configuration\" section of this document. By default, GDM is configured to display a face browser so the user can select their user account by clicking on an image instead of having to type their username. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI."

301

msgstr ""

302

303

#: C/gdm.xml:298(para)

304

msgid "After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, then runs the <filename>PreSession</filename> script as root. After running these scripts, the user session is started. When the user exits their session, the <filename>PostSession</filename> script is run as root. These scripts are provided as hooks for distributions and end-users to customize how sessions are managed. For example, using these hooks you could set up a machine which creates the user's $HOME directory on the fly, and erases it on logout. The difference between the <filename>PostLogin</filename> and <filename>PreSession</filename> scripts is that <filename>PostLogin</filename> is run before the pam_open_session call so is the right place to do anything which should be run before the user session is initialized. The <filename>PreSession</filename> script is called after session initialization."

305

msgstr ""

306

307

#: C/gdm.xml:318(title)

308

msgid "Greeter Panel"

309

msgstr ""

310

311

#: C/gdm.xml:319(para)

312

msgid "The GDM greeter program displays a panel docked at the bottom of the screen which provides additional functionality. When a user is selected, the panel allows the user to select which session, language, and keyboard layout to use after logging in. The keyboard layout selector also changes the keyboard layout used when typing your password. The panel also contains an area for login services to leave status icons. Some example status icons include a battery icon for current battery usage, and an icon for enabling accessibility features. The greeter program also provides buttons which allow the user to shutdown or restart the system. It is possible to configure GDM to not provide the shutdown and restart buttons, if desired. GDM can also be configured via PolicyKit (or via RBAC on Solaris) to require the user have appropriate authorization before accepting the shutdown or restart request."

313

msgstr ""

314

315

#: C/gdm.xml:336(para)

316

msgid "Note that keyboard layout features are only available on systems that support libxklavier."

317

msgstr ""

318

319

#: C/gdm.xml:343(title)

320

msgid "Accessibility"

321

msgstr ""

322

323

#: C/gdm.xml:345(para)

324

msgid "GDM supports \"Accessible Login\", allowing users to log into their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. Accessible Technology (AT) features such as an on-screen keyboard, screen reader, screen magnifier, and Xserver AccessX keyboard accessibility are available. It is also possible to enable large text or high contrast icons and controls, if needed. Refer to the \"Accessibility Configuration\" section of the document for more information how various accessibility features can be configured."

325

msgstr ""

326

327

#: C/gdm.xml:357(para)

328

msgid "On some Operating Systems, it is necessary to make sure that the GDM user is a member of the \"audio\" group for AT programs that require audio output (such as text-to-speech) to be functional."

329

msgstr ""

330

331

#: C/gdm.xml:365(title)

332

msgid "The GDM Face Browser"

333

msgstr ""

334

335

#: C/gdm.xml:367(para)

336

msgid "The Face Browser is the interface which allows users to select their username by clicking on an image. This feature can be enabled or disabled via the /apps/gdm/simple-greeter/disable_user_list GConf key and is on by default. When disabled, users must type their complete username by hand. When enabled, it displays all local users which are available for login on the system (all user accounts defined in the /etc/passwd file that have a valid shell and sufficiently high UID) and remote users that have recently logged in. The face browser in GDM 2.20 and earlier would attempt to display all remote users, which caused performance problems in large, enterprise deployments."

337

msgstr ""

338

339

#: C/gdm.xml:381(para)

340

msgid "The Face Browser is configured to display the users who log in most frequently at the top of the list. This helps to ensure that users who log in frequently can quickly find their login image."

341

msgstr ""

342

343

#: C/gdm.xml:387(para)

344

msgid "The Face Browser supports \"type-ahead search\" which dynamically moves the face selection as the user types to the corresponding username in the list. This means that a user with a long username will only have to type the first few characters of the username before the correct item in the list gets selected."

345

msgstr ""

346

347

#: C/gdm.xml:395(para)

348

msgid "The icons used by GDM can be installed globally by the sysadmin or can be located in the user's home directories. If installed globally they should be in the <filename><share>/pixmaps/faces/</filename> directory and the filename should be the name of the user. Face image files should be a standard image that GTK+ can read, such as PNG or JPEG. Face icons placed in the global face directory must be readable to the GDM user."

349

msgstr ""

350

351

#. <para>

352

#. TODO - In the old GDM the ~/gnome2/gdm file is used, but the new code

353

#. seems to use ~/.gnome/gdm. Error?

354

#. </para>

355

#: C/gdm.xml:411(para)

356

msgid "If there is no global icon for the user, GDM will look in the user's $HOME directory for the image file. GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for \"face/picture=\" in the <filename>~/.gnome2/gdm</filename> file."

357

msgstr ""

358

359

#: C/gdm.xml:420(para)

360

msgid "If a user has no defined face image, GDM will use the \"stock_person\" icon defined in the current GTK+ theme. If no such image is defined, it will fallback to a generic face image."

361

msgstr ""

362

363

#: C/gdm.xml:426(para)

364

msgid "Please note that loading and scaling face icons located in remote user home directories can be a very time-consuming task. Since it not practical to load images over NIS or NFS, GDM does not attempt to load face images from remote home directories."

365

msgstr ""

366

367

#: C/gdm.xml:433(para)

368

msgid "When the browser is turned on, valid usernames on the computer are exposed for everyone to see. If XDMCP is enabled, then the usernames are exposed to remote users. This, of course, limits security somewhat since a malicious user does not need to guess valid usernames. In some very restrictive environments the face browser may not be appropriate."

369

msgstr ""

370

371

#: C/gdm.xml:445(title)

372

msgid "XDMCP"

373

msgstr "XDMCP"

374

375

#. <para>

376

#. TODO - What XDMCP features actually work? I know that the

377

#. chooser is missing.

378

#. </para>

379

#: C/gdm.xml:454(para)

380

msgid "The GDM daemon can be configured to listen for and manage X Display Manage Protocol (XDMCP) requests from remote displays. By default XDMCP support is turned off, but can be enabled if desired. If GDM is built with TCP Wrapper support, then the daemon will only grant access to hosts specified in the GDM service section in the TCP Wrappers configuration file."

381

msgstr ""

382

383

#: C/gdm.xml:463(para)

384

msgid "GDM includes several measures making it more resistant to denial of service attacks on the XDMCP service. A lot of the protocol parameters, handshaking timeouts, etc. can be fine tuned. The default configuration should work reasonably on most systems."

385

msgstr ""

386

387

#: C/gdm.xml:470(para)

388

msgid "GDM by default listens for XDMCP requests on the normal UDP port used for XDMCP, port 177, and will respond to QUERY and BROADCAST_QUERY requests by sending a WILLING packet to the originator."

389

msgstr ""

390

391

#: C/gdm.xml:476(para)

392

msgid "GDM can also be configured to honor INDIRECT queries and present a host chooser to the remote display. GDM will remember the user's choice and forward subsequent requests to the chosen manager. GDM also supports an extension to the protocol which will make it forget the redirection once the user's connection succeeds. This extension is only supported if both daemons are GDM. It is transparent and will be ignored by XDM or other daemons that implement XDMCP."

393

msgstr ""

394

395

#: C/gdm.xml:486(para)

396

msgid "If XDMCP seems to not be working, make sure that all machines are specified in <filename>/etc/hosts</filename>."

397

msgstr ""

398

399

#: C/gdm.xml:491(para)

400

msgid "Refer to the \"Security\" section for information about security concerns when using XDMCP."

401

msgstr ""

402

403

#: C/gdm.xml:498(title)

404

msgid "Logging"

405

msgstr ""

406

407

#: C/gdm.xml:500(para)

408

msgid "GDM uses syslog to log errors and status. It can also log debugging information, which can be useful for tracking down problems if GDM is not working properly. Debug output can be enabled by setting the debug/Enable key to \"true\" in the <filename><etc>/gdm/custom.conf</filename> file."

409

msgstr ""

410

411

#: C/gdm.xml:508(para)

412

msgid "Output from the various Xservers is stored in the GDM log directory, which is normally <filename><var>/log/gdm/</filename>. Any Xserver messages are saved to a file associated with the display value, <filename><display>.log</filename>."

413

msgstr ""

414

415

#: C/gdm.xml:515(para)

416

msgid "The session output is piped through the GDM daemon to the <filename>~/.xsession-errors</filename> file. The file is overwritten on each login, so logging out and logging back into the same user via GDM will cause any messages from the previous session to be lost."

417

msgstr ""

418

419

#: C/gdm.xml:522(para)

420

msgid "Note that if GDM can not create this file for some reason, then a fallback file will be created named <filename>~/.xsession-errors.XXXXXXXX</filename> where the <filename>XXXXXXXX</filename> are some random characters."

421

msgstr ""

422

423

#: C/gdm.xml:530(title)

424

msgid "Fast User Switching"

425

msgstr ""

426

427

#: C/gdm.xml:532(para)

428

msgid "GDM allows multiple users to be logged in at the same time. After one user is logged in, additional users can log in via the User Switcher on the GNOME Panel, or from the \"Switch User\" button in Lock Screen dialog of GNOME Screensaver. The active session can be changed back and forth using the same mechanism. Note that some distributions may not add the User Switcher to the default panel configuration. It can be added using the panel context menu."

429

msgstr ""

430

431

#: C/gdm.xml:541(para)

432

msgid "Note this feature is available on systems that support Virtual Terminals. This feature will not function if Virtual Terminals is not available."

433

msgstr ""

434

435

#: C/gdm.xml:552(title)

436

msgid "Security"

437

msgstr "Varnost"

438

439

#: C/gdm.xml:555(title)

440

msgid "The GDM User And Group"

441

msgstr ""

442

443

#: C/gdm.xml:557(para)

444

msgid "For security reasons a dedicated user and group id are recommended for proper operation. This user and group are normally \"gdm\" on most systems, but can be configured to any user or group. All GDM GUI programs are run as this user, so that the programs which interact with the user are run in a sandbox. This user and group should have limited privilege."

445

msgstr ""

446

447

#: C/gdm.xml:566(para)

448

msgid "The only special privilege the \"gdm\" user requires is the ability to read and write Xauth files to the <filename><var>/run/gdm</filename> directory. The <filename><var>/run/gdm</filename> directory should have root:gdm ownership and 1777 permissions."

449

msgstr ""

450

451

#: C/gdm.xml:574(para)

452

msgid "You should not, under any circumstances, configure the GDM user/group to a user which a user could easily gain access to, such as the user <filename>nobody</filename>. Any user who gains access to an Xauth key can snoop on and control running GUI programs running in the associated session or perform a denial-of-service attack on it. It is important to ensure that the system is configured properly so that only the \"gdm\" user has access to these files and that it is not easy to login to this account. For example, the account should be setup to not have a password or allow non-root users to login to the account."

453

msgstr ""

454

455

#: C/gdm.xml:587(para)

456

msgid "The GDM greeter configuration is stored in GConf. To allow the GDM user to be able to write configuration, it is necessary for the \"gdm\" user to have a writable $HOME directory. Users may configure the default GConf configuration as desired to avoid the need to provide the \"gdm\" user with a writable $HOME directory. However, some features of GDM may be disabled if it is unable to write state information to GConf configuration."

457

msgstr ""

458

459

#: C/gdm.xml:599(title)

460

msgid "PAM"

461

msgstr "PAM"

462

463

#: C/gdm.xml:601(para)

464

msgid "GDM uses PAM for login authentication. PAM stands for Pluggable Authentication Module, and is used by most programs that request authentication on your computer. It allows the administrator to configure specific authentication behavior for different login programs (such as ssh, login GUI, screensaver, etc.)"

465

msgstr ""

466

467

#: C/gdm.xml:609(para)

468

msgid "PAM is complicated and highly configurable, and this documentation does not intend to explain this in detail. Instead, it is intended to give an overview of how PAM configuration relates with GDM, how PAM is commonly configured with GDM, and known issues. It is expected that a person needing to do PAM configuration would need to do further reading of PAM documentation to understand how to configure PAM and to understand terms used in this section."

469

msgstr ""

470

471

#: C/gdm.xml:619(para)

472

msgid "PAM configuration has different, but similar, interfaces on different Operating Systems, so check the <ulink type=\"help\" url=\"man:pam.d\">pam.d</ulink> or <ulink type=\"help\" url=\"man:pam.conf\">pam.conf</ulink> man page for details. Be sure you read the PAM documentation and are comfortable with the security implications of any changes you intend to make to your configuration."

473

msgstr ""

474

475

#: C/gdm.xml:629(para)

476

msgid "Note that, by default, GDM uses the \"gdm\" PAM service name for normal login and the \"gdm-autologin\" PAM service name for automatic login. These services may not be defined in your pam.d or pam.conf configured file. If there is no entry, then GDM will use the default PAM behavior. On most systems this should work fine. However, the automatic login feature may not work if the gdm-autologin service is not defined."

477

msgstr ""

478

479

#: C/gdm.xml:639(para)

480

msgid "The <filename>PostLogin</filename> script is run before pam_open_session is called, and the <filename>PreSession</filename> script is called after. This allows the system administrator to add any scripting to the login process either before or after PAM initializes the session."

481

msgstr ""

482

483

#: C/gdm.xml:647(para)

484

msgid "If you wish to make GDM work with other types of authentication mechanisms (such as a fingerprint or SmartCard reader), then you should implement this by using a PAM service module for the desired authentication type rather than by trying to modify the GDM code directly. Refer to the PAM documentation on your system. How to do this is frequently discussed on the <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information."

485

msgstr ""

486

487

#: C/gdm.xml:658(para)

488

msgid "PAM does have some limitations regarding being able to work with multiple types of authentication at the same time, like supporting the ability to accept either SmartCard and the ability to type the username and password into the login program. There are techniques that are used to make this work, and it is best to research how this problem is commonly solved when setting up such a configuration."

489

msgstr ""

490

491

#: C/gdm.xml:667(para)

492

msgid "If automatic login does not work on a system, check to see if the \"gdm-autologin\" PAM stack is defined in the PAM configuration. For this to work, it is necessary to use a PAM module that simply does no authentication, or which simply returns PAM_SUCCESS from all of its public interfaces. Assuming your system has a pam_allow.so PAM module which does this, a PAM configuration to enable \"gdm-autologin\" would look like this:"

493

msgstr ""

494

495

#: C/gdm.xml:677(screen)

496

#, no-wrap

497

msgid ""

498

"\n"

499

" gdm-autologin auth required pam_unix_cred.so.1\n"

500

" gdm-autologin auth sufficient pam_allow.so.1\n"

501

" gdm-autologin account sufficient pam_allow.so.1\n"

502

" gdm-autologin session sufficient pam_allow.so.1\n"

503

" gdm-autologin password sufficient pam_allow.so.1\n"

504

msgstr ""

505

506

#: C/gdm.xml:685(para)

507

msgid "The above setup will cause no lastlog entry to be generated. If a lastlog entry is desired, then use the following for the session:"

508

msgstr ""

509

510

#: C/gdm.xml:690(screen)

511

#, no-wrap

512

msgid ""

513

"\n"

514

" gdm-autologin session required pam_unix_session.so.1\n"

515

msgstr ""

516

517

#: C/gdm.xml:694(para)

518

msgid "If the computer is used by several people, which makes automatic login unsuitable, you may want to allow some users to log in without entering their password. This feature can be enabled as a per-user option in the users-admin tool from the gnome-system-tools; it is achieved by checking that the user is member a Unix group called \"nopasswdlogin\" before asking for a password. For this to work, the PAM configuration file for the \"gdm\" service must include a line such as:"

519

msgstr ""

520

521

#: C/gdm.xml:705(screen)

522

#, no-wrap

523

msgid ""

524

"\n"

525

" gdm auth sufficient pam_succeed_if.so user ingroup nopasswdlogin\n"

526

msgstr ""

527

528

#: C/gdm.xml:712(title)

529

msgid "utmp and wtmp"

530

msgstr ""

531

532

#: C/gdm.xml:714(para)

533

msgid "GDM generates utmp and wtmp User Accounting Database entries upon session login and logout. The utmp database contains user access and accounting information that is accessed by commands such as <command>finger</command>, <command>last</command>, <command>login</command>, and <command>who</command>. The wtmp database contains the history of user access and accounting information for the utmp database. Refer to the <ulink type=\"help\" url=\"man:utmp\">utmp</ulink> and <ulink type=\"help\" url=\"man:wtmp\">wtmp</ulink> man pages on your system for more information."

534

msgstr ""

535

536

#: C/gdm.xml:729(title)

537

msgid "Xserver Authentication Scheme"

538

msgstr ""

539

540

#: C/gdm.xml:731(para)

541

msgid "Xserver authorization files are stored in a newly created subdirectory of <filename><var>/run/gdm</filename> at start up. These files are used to store and share a \"password\" between X clients and the Xserver. This \"password\" is unique for each session logged in, so users from one session can't snoop on users from another."

542

msgstr ""

543

544

#: C/gdm.xml:739(para)

545

msgid "GDM only supports the MIT-MAGIC-COOKIE-1 Xserver authentication scheme. Normally little is gained from the other schemes, and no effort has been made to implement them so far. Be especially careful about using XDMCP because the Xserver authentication cookie goes over the wire as clear text. If snooping is possible, then an attacker could simply snoop your authentication password as you log in, regardless of the authentication scheme being used. If snooping is possible and undesirable, then you should use ssh for tunneling an X connection rather then using XDMCP. You could think of XDMCP as a sort of graphical telnet, having the same security issues. In most cases, ssh -Y should be preferred over GDM's XDMCP features."

546

msgstr ""

547

548

#: C/gdm.xml:756(title)

549

msgid "XDMCP Security"

550

msgstr ""

551

552

#: C/gdm.xml:758(para)

553

msgid "Even though your display is protected by cookies, XEvents and thus keystrokes typed when entering passwords will still go over the wire in clear text. It is trivial to capture these."

554

msgstr ""

555

556

#: C/gdm.xml:764(para)

557

msgid "XDMCP is primarily useful for running thin clients such as in terminal labs. Those thin clients will only ever need the network to access the server, and so it seems like the best security policy to have those thin clients on a separate network that cannot be accessed by the outside world, and can only connect to the server. The only point from which you need to access outside is the server. This type of set up should never use an unmanaged hub or other sniffable network."

558

msgstr ""

559

560

#: C/gdm.xml:777(title)

561

msgid "XDMCP Access Control"

562

msgstr ""

563

564

#: C/gdm.xml:779(para)

565

msgid "XDMCP access control is done using TCP wrappers. It is possible to compile GDM without TCP wrapper support, so this feature may not be supported on some Operating Systems."

566

msgstr ""

567

568

#: C/gdm.xml:785(para)

569

msgid "You should use the daemon name <command>gdm</command> in the <filename><etc>/hosts.allow</filename> and <filename><etc>/hosts.deny</filename> files. For example to deny computers from <filename>.evil.domain</filename> from logging in, then add"

570

msgstr ""

571

572

#: C/gdm.xml:792(screen)

573

#, no-wrap

574

msgid ""

575

"\n"

576

"gdm: .evil.domain\n"

577

msgstr ""

578

579

#: C/gdm.xml:795(para)

580

msgid "to <filename><etc>/hosts.deny</filename>. You may also need to add"

581

msgstr ""

582

583

#: C/gdm.xml:799(screen)

584

#, no-wrap

585

msgid ""

586

"\n"

587

"gdm: .your.domain\n"

588

msgstr ""

589

590

#: C/gdm.xml:802(para)

591

msgid "to your <filename><etc>/hosts.allow</filename> if you normally disallow all services from all hosts. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow(5)</ulink> man page for details."

592

msgstr ""

593

594

#: C/gdm.xml:811(title)

595

msgid "Firewall Security"

596

msgstr ""

597

598

#: C/gdm.xml:813(para)

599

msgid "Even though GDM tries to outsmart potential attackers trying to take advantage of XDMCP, it is still advised that you block the XDMCP port (normally UDP port 177) on your firewall unless really needed. GDM guards against denial of service attacks, but the X protocol is still inherently insecure and should only be used in controlled environments. Also each remote connection takes up lots of resources, so it is much easier to do a denial of service attack via XDMCP than attacking a webserver."

600

msgstr ""

601

602

#: C/gdm.xml:824(para)

603

msgid "It is also wise to block all of the Xserver ports. These are TCP ports 6000+ (one for each display number) on your firewall. Note that GDM will use display numbers 20 and higher for flexible on-demand servers."

604

msgstr ""

605

606

#: C/gdm.xml:831(para)

607

msgid "X is not a very safe protocol when using it over the Internet, and XDMCP is even less safe."

608

msgstr ""

609

610

#: C/gdm.xml:838(title)

611

msgid "PolicyKit"

612

msgstr ""

613

614

#. <para>

615

#. TODO - Should we say more?

616

#. </para>

617

#: C/gdm.xml:846(para)

618

msgid "GDM may be configured to use PolicyKit to allow the system administrator to control whether the login screen should provide the shutdown and restart buttons on the greeter screen."

619

msgstr ""

620

621

#: C/gdm.xml:852(para)

622

msgid "These buttons are controlled by the <filename>org.freedesktop.consolekit.system.stop-multiple-users</filename> and <filename>org.freedesktop.consolekit.system.restart-multiple-users</filename> actions respectively. Policy for these actions can be set up using the polkit-gnome-authorization tool, or the polkit-auth command line program."

623

msgstr ""

624

625

#: C/gdm.xml:864(title)

626

msgid "RBAC (Role Based Access Control)"

627

msgstr ""

628

629

#: C/gdm.xml:866(para)

630

msgid "GDM may be configured to use RBAC instead of PolicyKit. In this case the RBAC configuration is used to control whether the login screen should provide the shutdown and restart buttons on the greeter screen."

631

msgstr ""

632

633

#: C/gdm.xml:872(para)

634

msgid "For example, on Solaris, the \"solaris.system.shutdown\" authorization is used to control this. Simply modify the <filename>/etc/user_attr</filename> file so that the \"gdm\" user has this authorization."

635

msgstr ""

636

637

#: C/gdm.xml:885(title)

638

msgid "Support for ConsoleKit"

639

msgstr ""

640

641

#. <para>

642

#. TODO - Should we update these docs? Probably should mention any

643

#. configuration that users may want to do for using it with GDM?

644

#. If so, perhaps this section should be moved to a subsection of

645

#. the "Configure" section?

646

#. </para>

647

#: C/gdm.xml:896(para)

648

msgid "GDM includes support for publishing user login information with the user and login session accounting framework known as ConsoleKit. ConsoleKit is able to keep track of all the users currently logged in. In this respect, it can be used as a replacement for the utmp or utmpx files that are available on most Unix-like Operating Systems."

649

msgstr ""

650

651

#: C/gdm.xml:904(para)

652

msgid "When GDM is about to create a new login process for a user it will call a privileged method of ConsoleKit in order to open a new session for this user. At this time GDM also provides ConsoleKit with information about this user session such as: the user ID, the X11 Display name that will be associated with the session, the host-name from which the session originates (useful in the case of an XDMCP session), whether or not this session is attached, etc. As the entity that initiates the user process, GDM is in a unique position to know about the user session and to be trusted to provide these bits of information. The use of this privileged method is restricted by the use of the D-Bus system message bus security policy."

653

msgstr ""

654

655

#: C/gdm.xml:918(para)

656

msgid "In case a user with an existing session has authenticated at GDM and requests to resume that existing session, GDM calls a privileged method of ConsoleKit to unlock that session. The exact details of what happens when the session receives this unlock signal are undefined and session-specific. However, most sessions will unlock a screensaver in response."

657

msgstr ""

658

659

#: C/gdm.xml:927(para)

660

msgid "When the user chooses to log out, or if GDM or the session quit unexpectedly the user session will be unregistered from ConsoleKit."

661

msgstr ""

662

663

#: C/gdm.xml:936(title)

664

msgid "Configuration"

665

msgstr ""

666

667

#: C/gdm.xml:938(para)

668

msgid "GDM has a number of configuration interfaces. These include scripting integration points, daemon configuration, greeter configuration, general session settings, integration with gnome-settings-daemon configuration, and session configuration. These types of integration are described in detail below."

669

msgstr ""

670

671

#: C/gdm.xml:947(title)

672

msgid "Scripting Integration Points"

673

msgstr ""

674

675

#: C/gdm.xml:949(para)

676

msgid "The GDM script integration points can be found in the <filename><etc>/gdm/</filename> directory:"

677

msgstr ""

678

679

#: C/gdm.xml:954(screen)

680

#, no-wrap

681

msgid ""

682

"\n"

683

"Xsession\n"

684

"Init/\n"

685

"PostLogin/\n"

686

"PreSession/\n"

687

"PostSession/\n"

688

msgstr ""

689

690

#: C/gdm.xml:962(para)

691

msgid "The <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> scripts all work as described below."

692

msgstr ""

693

694

#: C/gdm.xml:968(para)

695

msgid "For each type of script, the default one which will be executed is called \"Default\" and is stored in a directory associated with the script type. So the default <filename>Init</filename> script is <filename><etc>/gdm/Init/Default</filename>. A per-display script can be provided, and if it exists it will be run instead of the default script. Such scripts are stored in the same directory as the default script and have the same name as the Xserver DISPLAY value for that display. For example, if the <filename><Init>/:0</filename> script exists, it will be run for DISPLAY \":0\"."

696

msgstr ""

697

698

#: C/gdm.xml:980(para)

699

msgid "All of these scripts are run with root privilege and return 0 if run successfully, and a non-zero return code if there was any failure that should cause the login session to be aborted. Also note that GDM will block until the scripts finish, so if any of these scripts hang, this will cause the login process to also hang."

700

msgstr ""

701

702

#: C/gdm.xml:988(para)

703

msgid "When the Xserver for the login GUI has been successfully started, but before the login GUI is actually displayed, GDM will run the <filename>Init</filename> script. This script is useful for starting programs that should be run while the login screen is showing, or for doing any special initialization if required."

704

msgstr ""

705

706

#: C/gdm.xml:996(para)

707

msgid "After the user has been successfully authenticated GDM will run the <filename>PostLogin</filename> script. This is done before any session setup has been done, including before the pam_open_session call. This script is useful for doing any session initialization that needs to happen before the session starts. For example, you might setup the user's $HOME directory if needed."

708

msgstr ""

709

710

#: C/gdm.xml:1005(para)

711

msgid "After the user session has been initialized, GDM will run the <filename>PreSession</filename> script. This script is useful for doing any session initialization that needs to happen after the session has been initialized. It can be used for session management or accounting, for example."

712

msgstr ""

713

714

#: C/gdm.xml:1013(para)

715

msgid "When a user terminates their session, GDM will run the <filename>PostSession</filename> script. Note that the Xserver will have been stopped by the time this script is run, so it should not be accessed."

716

msgstr ""

717

718

#: C/gdm.xml:1020(para)

719

msgid "Note that the <filename>PostSession</filename> script will be run even when the display fails to respond due to an I/O error or similar. Thus, there is no guarantee that X applications will work during script execution."

720

msgstr ""

721

722

#: C/gdm.xml:1027(para)

723

msgid "All of the above scripts will set the <filename>$RUNNING_UNDER_GDM</filename> environment variable to <filename>yes</filename>. If the scripts are also shared with other display managers, this allows you to identify when GDM is calling these scripts, so you can run specific code when GDM is used."

724

msgstr ""

725

726

#: C/gdm.xml:1037(title)

727

msgid "Autostart Configuration"

728

msgstr ""

729

730

#: C/gdm.xml:1039(para)

731

msgid "The <filename><share>/gdm/autostart/LoginWindow</filename> directory contains files in the format specified by the \"FreeDesktop.org Desktop Application Autostart Specification\". Standard features in the specification may be used to specify programs that should auto-restart or only be launched if a GConf configuration value is set, etc."

732

msgstr ""

733

734

#: C/gdm.xml:1048(para)

735

msgid "Any <filename>.desktop</filename> files in this directory will cause the associated program to automatically start with the login GUI greeter. By default, GDM is shipped with files which will autostart the gdm-simple-greeter login GUI greeter itself, the gnome-power-manager application, the gnome-settings-daemon, and the metacity window manager. These programs are needed for the greeter program to work. In addition, desktop files are provided for starting various AT programs if the configuration values specified in the Accessibility Configuration section below are set."

736

msgstr ""

737

738

#: C/gdm.xml:1062(title)

739

msgid "Xsession Script"

740

msgstr ""

741

742

#: C/gdm.xml:1064(para)

743

msgid "There is also an <filename>Xsession</filename> script located at <filename><etc>/gdm/Xsession</filename> which is called between the <filename>PreSession</filename> and the <filename>PostSession</filename> scripts. This script does not support per-display like the other scripts. This script is used for actually starting the user session. This script is run as the user, and it will run whatever session was specified by the Desktop session file the user selected to start."

744

msgstr ""

745

746

#: C/gdm.xml:1077(title)

747

msgid "Daemon Configuration"

748

msgstr ""

749

750

#: C/gdm.xml:1079(para)

751

msgid "The GDM daemon is configured using the <filename><etc>/gdm/custom.conf</filename> file. Default values are stored in GConf in the <filename>gdm.schemas</filename> file. It is recommended that end-users modify the <filename><etc>/gdm/custom.conf</filename> file because the schemas file may be overwritten when the user updates their system to have a newer version of GDM."

752

msgstr ""

753

754

#: C/gdm.xml:1089(para)

755

msgid "Note that older versions of GDM supported additional configuration options which are no longer supported in the latest versions of GDM."

756

msgstr ""

757

758

#: C/gdm.xml:1094(para)

759

msgid "The <filename><etc>/gdm/custom.conf</filename> file is in the <filename>keyfile</filename> format. Keywords in brackets define group sections, strings before an equal sign (=) are keys and the data after equal sign represents their value. Empty lines or lines starting with the hash mark (#) are ignored."

760

msgstr ""

761

762

#: C/gdm.xml:1102(para)

763

msgid "The file <filename><etc>/gdm/custom.conf</filename> supports the \"[daemon]\", \"[security]\", and \"[xdmcp]\" group sections. Within each group, there are particular key/value pairs that can be specified to modify how GDM behaves. For example, to enable timed login and specify the timed login user to be a user named \"you\", you would modify the file so it contains the following lines:"

764

msgstr ""

765

766

#: C/gdm.xml:1112(screen)

767

#, no-wrap

768

msgid ""

769

"\n"

770

"[daemon]\n"

771

"TimedLoginEnable=true\n"

772

"TimedLogin=you\n"

773

msgstr ""

774

775

#: C/gdm.xml:1118(para)

776

msgid "A full list of supported configuration keys follow:"

777

msgstr ""

778

779

#: C/gdm.xml:1123(title)

780

msgid "[chooser]"

781

msgstr ""

782

783

#: C/gdm.xml:1127(term)

784

msgid "Multicast"

785

msgstr ""

786

787

#: C/gdm.xml:1129(synopsis)

788

#, no-wrap

789

msgid "Multicast=false"

790

msgstr ""

791

792

#: C/gdm.xml:1130(para)

793

msgid "If true and IPv6 is enabled, the chooser will send a multicast query to the local network and collect responses from the hosts who have joined multicast group."

794

msgstr ""

795

796

#: C/gdm.xml:1139(term)

797

msgid "MulticastAddr"

798

msgstr ""

799

800

#: C/gdm.xml:1141(synopsis)

801

#, no-wrap

802

msgid "MulticastAddr=ff02::1"

803

msgstr ""

804

805

#: C/gdm.xml:1142(para)

806

msgid "This is the Link-local multicast address."

807

msgstr ""

808

809

#: C/gdm.xml:1151(title)

810

msgid "[daemon]"

811

msgstr ""

812

813

#: C/gdm.xml:1154(term)

814

msgid "TimedLoginEnable"

815

msgstr ""

816

817

#: C/gdm.xml:1156(synopsis)

818

#, no-wrap

819

msgid "TimedLoginEnable=false"

820

msgstr ""

821

822

#: C/gdm.xml:1157(para)

823

msgid "If the user given in <filename>TimedLogin</filename> should be logged in after a number of seconds (set with <filename>TimedLoginDelay</filename>) of inactivity on the login screen. This is useful for public access terminals or perhaps even home use. If the user uses the keyboard or browses the menus, the timeout will be reset to <filename>TimedLoginDelay</filename> or 30 seconds, whichever is higher. If the user does not enter a username but just hits the ENTER key while the login program is requesting the username, then GDM will assume the user wants to login immediately as the timed user. Note that no password will be asked for this user so you should be careful, although if using PAM it can be configured to require password entry before allowing login. Refer to the \"Security->PAM\" section of the manual for more information, or for help if this feature does not seem to work."

824

msgstr ""

825

826

#: C/gdm.xml:1179(term)

827

msgid "TimedLogin"

828

msgstr ""

829

830

#: C/gdm.xml:1181(synopsis)

831

#, no-wrap

832

msgid "TimedLogin="

833

msgstr ""

834

835

#: C/gdm.xml:1182(para)

836

msgid "This is the user that should be logged in after a specified number of seconds of inactivity."

837

msgstr ""

838

839

#: C/gdm.xml:1186(para)

840

#: C/gdm.xml:1230(para)

841

msgid "If the value ends with a vertical bar | (the pipe symbol), then GDM will execute the program specified and use whatever value is returned on standard out from the program as the user. The program is run with the DISPLAY environment variable set so that it is possible to specify the user in a per-display fashion. For example if the value is \"/usr/bin/getloginuser|\", then the program \"/usr/bin/getloginuser\" will be run to get the user value."

842

msgstr ""

843

844

#: C/gdm.xml:1200(term)

845

msgid "TimedLoginDelay"

846

msgstr ""

847

848

#: C/gdm.xml:1202(synopsis)

849

#, no-wrap

850

msgid "TimedLoginDelay=30"

851

msgstr ""

852

853

#: C/gdm.xml:1203(para)

854

msgid "Delay in seconds before the <filename>TimedLogin</filename> user will be logged in."

855

msgstr ""

856

857

#: C/gdm.xml:1211(term)

858

msgid "AutomaticLoginEnable"

859

msgstr ""

860

861

#: C/gdm.xml:1213(synopsis)

862

#, no-wrap

863

msgid "AutomaticLoginEnable=false"

864

msgstr ""

865

866

#: C/gdm.xml:1214(para)

867

msgid "If true, the user given in <filename>AutomaticLogin</filename> should be logged in immediately. This feature is like timed login with a delay of 0 seconds."

868

msgstr ""

869

870

#: C/gdm.xml:1223(term)

871

msgid "AutomaticLogin"

872

msgstr ""

873

874

#: C/gdm.xml:1225(synopsis)

875

#, no-wrap

876

msgid "AutomaticLogin="

877

msgstr ""

878

879

#: C/gdm.xml:1226(para)

880

msgid "This is the user that should be logged in immediately if <filename>AutomaticLoginEnable</filename> is true."

881

msgstr ""

882

883

#: C/gdm.xml:1244(term)

884

msgid "User"

885

msgstr "Uporabnik"

886

887

#: C/gdm.xml:1246(synopsis)

888

#, no-wrap

889

msgid "User=gdm"

890

msgstr ""

891

892

#: C/gdm.xml:1247(para)

893

msgid "The username under which the greeter and other GUI programs are run. Refer to the <filename>Group</filename> configuration key and to the \"Security->GDM User And Group\" section of this document for more information."

894

msgstr ""

895

896

#: C/gdm.xml:1257(term)

897

msgid "Group"

898

msgstr "Skupina"

899

900

#: C/gdm.xml:1259(synopsis)

901

#, no-wrap

902

msgid "Group=gdm"

903

msgstr ""

904

905

#: C/gdm.xml:1260(para)

906

msgid "The group name under which the greeter and other GUI programs are run. Refer to the <filename>User</filename> configuration key and to the \"Security->GDM User And Group\" section of this document for more information."

907

msgstr ""

908

909

#: C/gdm.xml:1272(title)

910

msgid "Debug Options"

911

msgstr ""

912

913

#: C/gdm.xml:1275(title)

914

msgid "[debug]"

915

msgstr ""

916

917

#: C/gdm.xml:1278(term)

918

#: C/gdm.xml:1408(term)

919

msgid "Enable"

920

msgstr ""

921

922

#: C/gdm.xml:1280(synopsis)

923

#: C/gdm.xml:1410(synopsis)

924

#, no-wrap

925

msgid "Enable=false"

926

msgstr ""

927

928

#: C/gdm.xml:1281(para)

929

msgid "To enable debugging, set the debug/Enable key to \"true\" in the <filename><etc>/gdm/custom.conf</filename> file and restart GDM. Then debug output will be sent to the system log file (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> depending on your Operating System)."

930

msgstr ""

931

932

#: C/gdm.xml:1296(title)

933

msgid "Greeter Options"

934

msgstr ""

935

936

#: C/gdm.xml:1299(title)

937

msgid "[greeter]"

938

msgstr ""

939

940

#: C/gdm.xml:1302(term)

941

msgid "IncludeAll"

942

msgstr ""

943

944

#: C/gdm.xml:1304(synopsis)

945

#, no-wrap

946

msgid "IncludeAll=true"

947

msgstr ""

948

949

#: C/gdm.xml:1305(para)

950

msgid "If true, then the face browser will show all users on the local machine. If false, the face browser will only show users who have recently logged in."

951

msgstr ""

952

953

#: C/gdm.xml:1311(para)

954

msgid "When this key is true, GDM will call fgetpwent() to get a list of local users on the system. Any users with a user id less than 500 (or 100 if running on Solaris) are filtered out. The Face Browser also will display any users that have previously logged in on the system (for example NIS/LDAP users). It gets this list via calling the <command>ck-history</command> ConsoleKit interface. It will also filter out any users which do not have a valid shell (valid shells are any shell that getusershell() returns - /sbin/nologin or /bin/false are considered invalid shells even if getusershell() returns them)."

955

msgstr ""

956

957

#: C/gdm.xml:1324(para)

958

msgid "If false, then GDM more simply only displays users that have previously logged in on the system (local or NIS/LDAP users) by calling the <command>ck-history</command> ConsoleKit interface."

959

msgstr ""

960

961

#: C/gdm.xml:1333(term)

962

msgid "Include"

963

msgstr ""

964

965

#: C/gdm.xml:1335(synopsis)

966

#, no-wrap

967

msgid "Include="

968

msgstr ""

969

970

#: C/gdm.xml:1336(para)

971

msgid "Set to a list of users to always include in the Face Browser. This value is set to a list of users separated by commas. By default, the value is empty."

972

msgstr ""

973

974

#: C/gdm.xml:1345(term)

975

msgid "Exclude"

976

msgstr ""

977

978

#: C/gdm.xml:1347(synopsis)

979

#, no-wrap

980

msgid "Exclude=bin,root,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,nobody4,noaccess,postgres,pvm,rpm,nfsnobody,pcap"

981

msgstr ""

982

983

#: C/gdm.xml:1348(para)

984

msgid "Set to a list of users to always exclude in the Face Browser. This value is set to a list of users separated by commas. Note that the setting in the <filename>custom.conf</filename> overrides the default value, so if you wish to add additional users to the list, then you need to set the value to the default value with additional users appended to the list."

985

msgstr ""

986

987

#: C/gdm.xml:1362(title)

988

msgid "Security Options"

989

msgstr ""

990

991

#: C/gdm.xml:1365(title)

992

msgid "[security]"

993

msgstr ""

994

995

#: C/gdm.xml:1368(term)

996

msgid "DisallowTCP"

997

msgstr ""

998

999

#: C/gdm.xml:1370(synopsis)

1000

#, no-wrap

1001

msgid "DisallowTCP=true"

1002

msgstr ""

1003

1004

#: C/gdm.xml:1371(para)

1005

msgid "If true, then always append <filename>-nolisten tcp</filename> to the command line when starting attached Xservers, thus disallowing TCP connection. This is a more secure configuration if you are not using remote connections."

1006

msgstr ""

1007

1008

#: C/gdm.xml:1383(title)

1009

msgid "XDCMP Support"

1010

msgstr ""

1011

1012

#: C/gdm.xml:1386(title)

1013

msgid "[xdmcp]"

1014

msgstr ""

1015

1016

#: C/gdm.xml:1389(term)

1017

msgid "DisplaysPerHost"

1018

msgstr ""

1019

1020

#: C/gdm.xml:1391(synopsis)

1021

#, no-wrap

1022

msgid "DisplaysPerHost=1"

1023

msgstr ""

1024

1025

#: C/gdm.xml:1392(para)

1026

msgid "To prevent attackers from filling up the pending queue, GDM will only allow one connection for each remote computer. If you want to provide display services to computers with more than one screen, you should increase this value."

1027

msgstr ""

1028

1029

#: C/gdm.xml:1399(para)

1030

msgid "Note that the number of attached DISPLAYS allowed is not limited. Only remote connections via XDMCP are limited by this configuration option."

1031

msgstr ""

1032

1033

#: C/gdm.xml:1411(para)

1034

msgid "Setting this to true enables XDMCP support allowing remote displays/X terminals to be managed by GDM."

1035

msgstr ""

1036

1037

#: C/gdm.xml:1416(para)

1038

msgid "<filename>gdm</filename> listens for requests on UDP port 177. See the Port option for more information."

1039

msgstr ""

1040

1041

#: C/gdm.xml:1421(para)

1042

msgid "If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is <filename>gdm</filename>"

1043

msgstr ""

1044

1045

#: C/gdm.xml:1427(para)

1046

msgid ""

1047

"You should add <screen>\n"

1048

"gdm:.my.domain\n"

1049

"</screen> to your <filename><etc>/hosts.allow</filename>, depending on your TCP Wrappers configuration. See the <ulink type=\"help\" url=\"man:hosts.allow\">hosts.allow</ulink> man page for details."

1050

msgstr ""

1051

1052

#: C/gdm.xml:1438(para)

1053

msgid "Please note that XDMCP is not a particularly secure protocol and that it is a good idea to block UDP port 177 on your firewall unless you really need it."

1054

msgstr ""

1055

1056

#: C/gdm.xml:1447(term)

1057

msgid "HonorIndirect"

1058

msgstr ""

1059

1060

#: C/gdm.xml:1449(synopsis)

1061

#, no-wrap

1062

msgid "HonorIndirect=true"

1063

msgstr ""

1064

1065

#: C/gdm.xml:1450(para)

1066

msgid "Enables XDMCP INDIRECT choosing (i.e. remote execution of <filename>gdmchooser</filename>) for X-terminals which do not supply their own display browser."

1067

msgstr ""

1068

1069

#: C/gdm.xml:1459(term)

1070

msgid "MaxPending"

1071

msgstr ""

1072

1073

#: C/gdm.xml:1461(synopsis)

1074

#, no-wrap

1075

msgid "MaxPending=4"

1076

msgstr ""

1077

1078

#: C/gdm.xml:1462(para)

1079

msgid "To avoid denial of service attacks, GDM has fixed size queue of pending connections. Only MaxPending displays can start at the same time."

1080

msgstr ""

1081

1082

#: C/gdm.xml:1468(para)

1083

msgid "Please note that this parameter does not limit the number of remote displays which can be managed. It only limits the number of displays initiating a connection simultaneously."

1084

msgstr ""

1085

1086

#: C/gdm.xml:1477(term)

1087

msgid "MaxSessions"

1088

msgstr ""

1089

1090

#: C/gdm.xml:1479(synopsis)

1091

#, no-wrap

1092

msgid "MaxSessions=16"

1093

msgstr ""

1094

1095

#: C/gdm.xml:1480(para)

1096

msgid "Determines the maximum number of remote display connections which will be managed simultaneously. I.e. the total number of remote displays that can use your host."

1097

msgstr ""

1098

1099

#: C/gdm.xml:1489(term)

1100

msgid "MaxWait"

1101

msgstr ""

1102

1103

#: C/gdm.xml:1491(synopsis)

1104

#, no-wrap

1105

msgid "MaxWait=30"

1106

msgstr ""

1107

1108

#: C/gdm.xml:1492(para)

1109

msgid "When GDM is ready to manage a display an ACCEPT packet is sent to it containing a unique session id which will be used in future XDMCP conversations."

1110

msgstr ""

1111

1112

#: C/gdm.xml:1498(para)

1113

msgid "GDM will then place the session id in the pending queue waiting for the display to respond with a MANAGE request."

1114

msgstr ""

1115

1116

#: C/gdm.xml:1503(para)

1117

msgid "If no response is received within MaxWait seconds, GDM will declare the display dead and erase it from the pending queue freeing up the slot for other displays."

1118

msgstr ""

1119

1120

#: C/gdm.xml:1512(term)

1121

msgid "MaxWaitIndirect"

1122

msgstr ""

1123

1124

#: C/gdm.xml:1514(synopsis)

1125

#, no-wrap

1126

msgid "MaxWaitIndirect=30"

1127

msgstr ""

1128

1129

#: C/gdm.xml:1515(para)

1130

msgid "The MaxWaitIndirect parameter determines the maximum number of seconds between the time where a user chooses a host and the subsequent indirect query where the user is connected to the host. When the timeout is exceeded, the information about the chosen host is forgotten and the indirect slot freed up for other displays. The information may be forgotten earlier if there are more hosts trying to send indirect queries then <filename>MaxPendingIndirect</filename>."

1131

msgstr ""

1132

1133

#: C/gdm.xml:1529(term)

1134

msgid "PingIntervalSeconds"

1135

msgstr ""

1136

1137

#: C/gdm.xml:1531(synopsis)

1138

#, no-wrap

1139

msgid "PingIntervalSeconds=60"

1140

msgstr ""

1141

1142

#: C/gdm.xml:1532(para)

1143

msgid "If the Xserver does not respond in the specified number of seconds, then the connection is stopped and the session ended. When this happens the slave daemon dies with an ALARM signal. Note that GDM 2.20 and earlier multiplied this setting by 2, so it may be necessary to increase the timeout if upgrading from GDM 2.20 and earlier to a newer version."

1144

msgstr ""

1145

1146

#: C/gdm.xml:1541(para)

1147

msgid "Note that GDM in the past used to have a <filename>PingInterval</filename> configuration key which was also in minutes. For most purposes you'd want this setting to be lower than one minute. However since in most cases where XDMCP would be used (such as terminal labs), a lag of more than 15 or so seconds would really mean that the terminal was turned off or restarted and you would want to end the session."

1148

msgstr ""

1149

1150

#: C/gdm.xml:1554(term)

1151

msgid "Port"

1152

msgstr ""

1153

1154

#: C/gdm.xml:1556(synopsis)

1155

#, no-wrap

1156

msgid "Port=177"

1157

msgstr ""

1158

1159

#: C/gdm.xml:1557(para)

1160

msgid "The UDP port number <filename>gdm</filename> should listen to for XDMCP requests. Do not change this unless you know what you are doing."

1161

msgstr ""

1162

1163

#: C/gdm.xml:1566(term)

1164

msgid "Willing"

1165

msgstr ""

1166

1167

#: C/gdm.xml:1568(synopsis)

1168

#, no-wrap

1169

msgid "Willing=<etc>/gdm/Xwilling"

1170

msgstr ""

1171

1172

#: C/gdm.xml:1569(para)

1173

msgid "When the machine sends a WILLING packet back after a QUERY it sends a string that gives the current status of this server. The default message is the system ID, but it is possible to create a script that displays customized message. If this script does not exist or this key is empty the default message is sent. If this script succeeds and produces some output, the first line of it's output is sent (and only the first line). It runs at most once every 3 seconds to prevent possible denial of service by flooding the machine with QUERY packets."

1174

msgstr ""

1175

1176

#: C/gdm.xml:1588(title)

1177

msgid "Simple Greeter Configuration"

1178

msgstr ""

1179

1180

#: C/gdm.xml:1590(para)

1181

msgid "The GDM default greeter is called the simple Greeter and is configured via GConf. Default values are stored in GConf in the <filename>gdm-simple-greeter.schemas</filename> file. These defaults can be overridden if the \"gdm\" user has a writable $HOME directory to store GConf settings. These values can be edited using the <command>gconftool-2</command> or <command>gconf-editor</command> programs. The following configuration options are supported:"

1182

msgstr ""

1183

1184

#: C/gdm.xml:1601(title)

1185

msgid "Greeter Configuration Keys"

1186

msgstr ""

1187

1188

#: C/gdm.xml:1604(term)

1189

msgid "/apps/gdm/simple-greeter/banner_message_enable"

1190

msgstr ""

1191

1192

#: C/gdm.xml:1606(synopsis)

1193

#: C/gdm.xml:1627(synopsis)

1194

#: C/gdm.xml:1638(synopsis)

1195

#: C/gdm.xml:1703(synopsis)

1196

#: C/gdm.xml:1768(synopsis)

1197

#: C/gdm.xml:1779(synopsis)

1198

#: C/gdm.xml:1790(synopsis)

1199

#: C/gdm.xml:1801(synopsis)

1200

#, no-wrap

1201

msgid "false (boolean)"

1202

msgstr ""

1203

1204

#: C/gdm.xml:1607(para)

1205

msgid "Controls whether the banner message text is displayed."

1206

msgstr ""

1207

1208

#: C/gdm.xml:1614(term)

1209

msgid "/apps/gdm/simple-greeter/banner_message_text"

1210

msgstr ""

1211

1212

#: C/gdm.xml:1616(synopsis)

1213

#, no-wrap

1214

msgid "NULL (string)"

1215

msgstr ""

1216

1217

#: C/gdm.xml:1617(para)

1218

msgid "Specifies the text banner message to show on the greeter window."

1219

msgstr ""

1220

1221

#: C/gdm.xml:1625(term)

1222

msgid "/apps/gdm/simple-greeter/disable_restart_buttons"

1223

msgstr ""

1224

1225

#: C/gdm.xml:1628(para)

1226

msgid "Controls whether to show the restart buttons in the login window."

1227

msgstr ""

1228

1229

#: C/gdm.xml:1636(term)

1230

msgid "/apps/gdm/simple-greeter/disable_user_list"

1231

msgstr ""

1232

1233

#: C/gdm.xml:1639(para)

1234

msgid "If true, then the face browser with known users is not shown in the login window."

1235

msgstr ""

1236

1237

#: C/gdm.xml:1647(term)

1238

msgid "/apps/gdm/simple-greeter/logo_icon_name"

1239

msgstr ""

1240

1241

#: C/gdm.xml:1649(synopsis)

1242

#, no-wrap

1243

msgid "computer (string)"

1244

msgstr ""

1245

1246

#: C/gdm.xml:1650(para)

1247

msgid "Set to the themed icon name to use for the greeter logo."

1248

msgstr ""

1249

1250

#: C/gdm.xml:1657(term)

1251

msgid "/apps/gdm/simple-greeter/recent-languages"

1252

msgstr ""

1253

1254

#: C/gdm.xml:1659(synopsis)

1255

#: C/gdm.xml:1681(synopsis)

1256

#, no-wrap

1257

msgid "[] (string list)"

1258

msgstr ""

1259

1260

#: C/gdm.xml:1660(para)

1261

msgid "Set to a list of languages to be shown by default in the login window. Default value is \"[]\". With the default setting only the system default language is shown and the option \"Other...\" which pops-up a dialog box showing a full list of available languages which the user can select."

1262

msgstr ""

1263

1264

#: C/gdm.xml:1668(para)

1265

msgid "Users are not intended to change this setting by hand. Instead GDM keeps track of any languages selected in this configuration key, and will show them in the language combo box along with the \"Other...\" choice. This way, commonly selected languages are easier to select."

1266

msgstr ""

1267

1268

#: C/gdm.xml:1679(term)

1269

msgid "/apps/gdm/simple-greeter/recent-layouts"

1270

msgstr ""

1271

1272

#: C/gdm.xml:1682(para)

1273

msgid "Set to a list of keyboard layouts to be shown by default in the login panel. Default value is \"[]\". With the default setting only the system default keyboard layout is shown and the option \"Other...\" which pops-up a dialog box showing a full list of available keyboard layouts which the user can select."

1274

msgstr ""

1275

1276

#: C/gdm.xml:1690(para)

1277

msgid "Users are not intended to change this setting by hand. Instead GDM keeps track of any keyboard layouts selected in this configuration key, and will show them in the keyboard layout combo box along with the \"Other...\" choice. This way, commonly selected keyboard layouts are easier to select."

1278

msgstr ""

1279

1280

#: C/gdm.xml:1701(term)

1281

msgid "/apps/gdm/simple-greeter/wm_use_compiz"

1282

msgstr ""

1283

1284

#: C/gdm.xml:1704(para)

1285

msgid "Controls whether compiz is used as the window manager instead of metacity."

1286

msgstr ""

1287

1288

#: C/gdm.xml:1714(title)

1289

msgid "Accessibility Configuration"

1290

msgstr ""

1291

1292

#: C/gdm.xml:1716(para)

1293

msgid "This section describes the accessibility configuration options available in GDM."

1294

msgstr ""

1295

1296

#: C/gdm.xml:1722(title)

1297

msgid "GDM Accessibility Dialog And GConf Keys"

1298

msgstr ""

1299

1300

#: C/gdm.xml:1724(para)

1301

msgid "The GDM greeter panel at the login screen displays an accessibility icon. Clicking on that icon opens the GDM Accessibility Dialog. In the GDM Accessibility Dialog, there is a list of checkboxes, so the user can enable or disable the associated assistive tools."

1302

msgstr ""

1303

1304

#: C/gdm.xml:1731(para)

1305

msgid "The checkboxes that correspond to the on-screen keyboard, screen magnifier and screen reader assistive tools act on the three GConf keys that are described in the next section of this document. By enabling or disabling these checkboxes, the associated GConf key is set to \"true\" or \"false\". When the GConf key is set to true, the assistive tools linked to this GConf key are launched. When the GConf key is set to \"false\", any running assistive tool linked to this GConf key are terminated. These GConf keys are not automatically reset to a default state after the user has logged in. Consequently, the assistive tools that were running during the last GDM login session will automatically be launched at the next GDM login session."

1306

msgstr ""

1307

1308

#: C/gdm.xml:1745(para)

1309

msgid "The other checkboxes in the GDM Accessibility Dialog do not have corresponding GConf keys because no additional program is launched to provide the accessibility features that they offer. These other options correspond to accessibility features that are provided by the Xserver, which is always running during the GDM session."

1310

msgstr ""

1311

1312

#: C/gdm.xml:1755(title)

1313

msgid "Accessibility GConf Keys"

1314

msgstr ""

1315

1316

#: C/gdm.xml:1757(para)

1317

msgid "GDM offers the following GConf keys to control its accessibility features:"

1318

msgstr ""

1319

1320

#: C/gdm.xml:1763(title)

1321

msgid "GDM Configuration Keys"

1322

msgstr ""

1323

1324

#: C/gdm.xml:1766(term)

1325

msgid "/desktop/gnome/interface/accessibility"

1326

msgstr ""

1327

1328

#: C/gdm.xml:1769(para)

1329

msgid "Controls whether the Accessibility infrastructure will be started with the GDM GUI. This is needed for many accessibility technology programs to work."

1330

msgstr ""

1331

1332

#: C/gdm.xml:1777(term)

1333

msgid "/desktop/gnome/applications/at/screen_magnifier_enabled"

1334

msgstr ""

1335

1336

#: C/gdm.xml:1780(para)

1337

msgid "If set, then the assistive tools linked to this GConf key will be started with the GDM GUI program. By default this is a screen magnifier application."

1338

msgstr ""

1339

1340

#: C/gdm.xml:1788(term)

1341

msgid "/desktop/gnome/applications/at/screen_keyboard_enabled"

1342

msgstr ""

1343

1344

#: C/gdm.xml:1791(para)

1345

msgid "If set, then the assistive tools linked to this GConf key will be started with the GDM GUI program. By default this is an on-screen keyboard application."

1346

msgstr ""

1347

1348

#: C/gdm.xml:1799(term)

1349

msgid "/desktop/gnome/applications/at/screen_reader_enabled"

1350

msgstr ""

1351

1352

#: C/gdm.xml:1802(para)

1353

msgid "If set, then the assistive tools linked to this GConf key will be started with the GDM GUI program. By default this is a screen reader application."

1354

msgstr ""

1355

1356

#: C/gdm.xml:1813(title)

1357

msgid "Linking GConf Keys to Accessbility Tools"

1358

msgstr ""

1359

1360

#: C/gdm.xml:1815(para)

1361

msgid "For the screen_magnifier_enabled, the screen_keyboard_enabled, and the screen_reader_enabled GConf keys, the assistive tool which gets launched depends on the desktop files located in the GDM autostart directory as described in the \"Autostart Configuration\" section of this manual. Any desktop file in the GDM autostart directory can be linked to these GConf key via specifying that GConf key in the AutostartCondition value in the desktop file. So the exact AutostartCondition line in the desktop file could be one of the following:"

1362

msgstr ""

1363

1364

#: C/gdm.xml:1827(screen)

1365

#, no-wrap

1366

msgid ""

1367

"\n"

1368

"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"

1369

"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_magnifier_enabled\n"

1370

"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled\n"

1371

msgstr ""

1372

1373

#: C/gdm.xml:1833(para)

1374

msgid "When an accessibility key is true, then any program which is linked to that key in a GDM autostart desktop file will be launched (unless the Hidden key is set to true in that desktop file). A single GConf key can even start multiple assistive tools if there are multiple desktop files with this AutostartCondition in the GDM autostart directory."

1375

msgstr ""

1376

1377

#: C/gdm.xml:1843(title)

1378

msgid "Example Of Modifying Accessibility Tool Configuration"

1379

msgstr ""

1380

1381

#: C/gdm.xml:1845(para)

1382

msgid "For example, if GNOME is distributed with GOK as the default on-screen keyboard, then this could be replaced with a different program if desired. To replace GOK with the on-screen keyboard application \"onboard\" and additionally activate the assistive tool \"mousetweaks\" for dwelling support, then the following configuration is needed."

1383

msgstr ""

1384

1385

#: C/gdm.xml:1853(para)

1386

msgid "Create a desktop file for onboard and a second one for mousetweaks; for example, onboard.desktop and mousetweaks.desktop. These files must be placed in the GDM autostart directory and be in the format as explained in the \"Autostart Configuration\" section of this document."

1387

msgstr ""

1388

1389

#: C/gdm.xml:1861(para)

1390

msgid "The following is an example <filename>onboard.desktop</filename> file:"

1391

msgstr ""

1392

1393

#: C/gdm.xml:1865(screen)

1394

#, no-wrap

1395

msgid ""

1396

"\n"

1397

"[Desktop Entry]\n"

1398

"Encoding=UTF-8\n"

1399

"Name=Onboard Onscreen Keyboard\n"

1400

"Comment=Use an on-screen keyboard\n"

1401

"TryExec=onboard\n"

1402

"Exec=onboard --size 500x180 -x 20 -y 10\n"

1403

"Terminal=false\n"

1404

"Type=Application\n"

1405

"StartupNotify=true\n"

1406

"Categories=GNOME;GTK;Accessibility;\n"

1407

"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"

1408

msgstr ""

1409

1410

#: C/gdm.xml:1879(para)

1411

msgid "The following is an example <filename>mousetweaks.desktop</filename> file:"

1412

msgstr ""

1413

1414

#: C/gdm.xml:1884(screen)

1415

#, no-wrap

1416

msgid ""

1417

"\n"

1418

"[Desktop Entry]\n"

1419

"Encoding=UTF-8\n"

1420

"Name=Software Mouse-Clicks\n"

1421

"Comment=Perform clicks by dwelling with the pointer\n"

1422

"TryExec=mousetweaks\n"

1423

"Exec=mousetweaks --enable-dwell -m window -c -x 20 -y 240 \n"

1424

"Terminal=false\n"

1425

"Type=Application\n"

1426

"StartupNotify=true\n"

1427

"Categories=GNOME;GTK;Accessibility;\n"

1428

"AutostartCondition=GNOME /desktop/gnome/applications/at/screen_keyboard_enabled\n"

1429

msgstr ""

1430

1431

#: C/gdm.xml:1898(para)

1432

msgid "Note the line with the AutostartCondition that links both desktop files to the GConf key for the on-screen keyboard."

1433

msgstr ""

1434

1435

#: C/gdm.xml:1903(para)

1436

msgid "To disable GOK from starting, the desktop file for the GOK on-screen keyboard must be removed or deactivated. Otherwise onboard and GOK would simultaneously be started. This can be done by removing the gok.desktop file from the GDM autostart directory, or by adding the \"Hidden=true\" key setting to the gok.desktop file."

1437

msgstr ""

1438

1439

#: C/gdm.xml:1911(para)

1440

msgid "After making these changes, GOK will no longer be started when the user activates the on-screen keyboard in the GDM session; but onboard and mousetweaks will instead be launched."

1441

msgstr ""

1442

1443

#: C/gdm.xml:1920(title)

1444

msgid "General Session Settings"

1445

msgstr ""

1446

1447

#. <para>

1448

#. TODO - I think this section should be expanded upon. What specific

1449

#. keys are of interest, or would some users be likely to want

1450

#. to configure? Also, would be good to be more specific about

1451

#. how lock down management is handled.

1452

#. </para>

1453

#: C/gdm.xml:1929(para)

1454

msgid "The GDM Greeter uses some of the same framework that your desktop session will use. And so, it is influenced by a number of the same GConf settings. For each of these settings the Greeter will use the default value unless it is specifically overridden by a) GDM's installed mandatory policy b) system mandatory policy. GDM installs its own mandatory policy to lock down some settings for security."

1455

msgstr ""

1456

1457

#: C/gdm.xml:1940(title)

1458

msgid "GNOME Settings Daemon"

1459

msgstr ""

1460

1461

#. <para>

1462

#. TODO - I think this section should be expanded upon. What specific

1463

#. keys are of interest, or would some users be likely to want

1464

#. to configure? Also, would be good to give a more complete

1465

#. list of plugins that users might want to consider disabling.

1466

#. Also, shouldn't we list the sound/active key in the Greeter

1467

#. configuration setting? Oddly I do not find this key used

1468

#. in anything but the chooser in SVN.

1469

#. </para>

1470

#: C/gdm.xml:1953(para)

1471

msgid "GDM enables the following gnome-settings-daemon plugins: a11y-keyboard, background, sound, xsettings."

1472

msgstr ""

1473

1474

#: C/gdm.xml:1958(para)

1475

msgid "These are responsible for things like the background image, font and theme settings, sound events, etc."

1476

msgstr ""

1477

1478

#: C/gdm.xml:1963(para)

1479

msgid "Plugins can also be disabled using GConf. For example, if you want to disable the sound plugin then unset the following key: <filename>/apps/gdm/simple-greeter/settings-manager-plugins/sound/active</filename>."

1480

msgstr ""

1481

1482

#: C/gdm.xml:1971(title)

1483

msgid "GDM Session Configuration"

1484

msgstr ""

1485

1486

#: C/gdm.xml:1973(para)

1487

msgid "GDM sessions are specified using the FreeDesktop.org Desktop Entry Specification, which can be referenced at the following URL: <ulink url=\"http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec\"> http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec</ulink>."

1488

msgstr ""

1489

1490

#: C/gdm.xml:1980(para)

1491

msgid "By default, GDM will install desktop files in the <filename><share>/xsessions</filename> directory. GDM will search the following directories in this order to find desktop files: <filename><etc>/X11/sessions/</filename>, <filename><dmconfdir>/Sessions</filename>, <filename><share>/xsessions</filename>, and <filename><share>/gdm/BuiltInSessions</filename>. By default the <filename><dmconfdir></filename> is set to <filename><etc>/dm/</filename> unless GDM is configured to use a different directory via the \"--with-dmconfdir\" option."

1492

msgstr ""

1493

1494

#: C/gdm.xml:1993(para)

1495

msgid "A session can be disabled by editing the desktop file and adding a line as follows: <filename>Hidden=true</filename>."

1496

msgstr ""

1497

1498

#: C/gdm.xml:1998(para)

1499

msgid "GDM desktop files support a GDM-specific extension, a key named \"X-GDM-BypassXsession\". If the key is not specified in a desktop file, the value defaults to \"false\". If this key is specified to be \"true\" in a desktop file, then GDM will launch the program specified by the desktop file \"Exec\" key directly when starting the user session. It will not run the program via the <filename><etc>/gdm/Xsession</filename> script, which is the normal behavior. Since bypassing the <filename><etc>/gdm/Xsession</filename> script avoids setting up the user session with the normal system and user settings, sessions started this way can be useful for debugging problems in the system or user scripts that might be preventing a user from being able to start a session."

1500

msgstr ""

1501

1502

#: C/gdm.xml:2017(title)

1503

msgid "GDM User Session and Language Configuration"

1504

msgstr ""

1505

1506

#: C/gdm.xml:2018(para)

1507

msgid "The user's default session and language choices are stored in the <filename>~/.dmrc</filename> file. When a user logs in for the first time, this file is created with the user's initial choices. The user can change these default values by simply changing to a different value when logging in. GDM will remember this change for subsequent logins."

1508

msgstr ""

1509

1510

#: C/gdm.xml:2026(para)

1511

msgid "The <filename>~/.dmrc</filename> file is in the standard <filename>INI</filename> format. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>."

1512

msgstr ""

1513

1514

#: C/gdm.xml:2033(para)

1515

msgid "The <filename>Session</filename> key specifies the basename of the session <filename>.desktop</filename> file that the user wishes to normally use without the <filename>.desktop</filename> extension. The <filename>Language</filename> key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:"

1516

msgstr ""

1517

1518

#: C/gdm.xml:2042(screen)

1519

#, no-wrap

1520

msgid ""

1521

"\n"

1522

"[Desktop]\n"

1523

"Session=gnome\n"

1524

"Language=cs_CZ.UTF-8\n"

1525

msgstr ""

1526

1527

#: C/gdm.xml:2054(title)

1528

msgid "GDM Commands"

1529

msgstr ""

1530

1531

#: C/gdm.xml:2057(title)

1532

msgid "GDM Root User Commands"

1533

msgstr ""

1534

1535

#: C/gdm.xml:2059(para)

1536

msgid "The GDM package provides the following commands in <filename>sbindir</filename> intended to be run by the root user:"

1537

msgstr ""

1538

1539

#: C/gdm.xml:2065(title)

1540

#: C/gdm.xml:2080(title)

1541

msgid "<command>gdm</command> and <command>gdm-binary</command> Command Line Options"

1542

msgstr ""

1543

1544

#: C/gdm.xml:2068(para)

1545

msgid "The <command>gdm</command> command is really just a script which runs the <command>gdm-binary</command>, passing along any options. Before launching <command>gdm-binary</command>, the gdm wrapper script will source the <filename><etc>/profile</filename> file to set the standard system environment variables. In order to better support internationalization, it will also set the LC_MESSAGES environment variable to LANG if neither LC_MESSAGES or LC_ALL are set. The <command>gdm-binary</command> is the actual GDM daemon."

1546

msgstr ""

1547

1548

#: C/gdm.xml:2084(term)

1549

msgid "-?, --help"

1550

msgstr ""

1551

1552

#: C/gdm.xml:2086(para)

1553

msgid "Gives a brief overview of the command line options."

1554

msgstr ""

1555

1556

#: C/gdm.xml:2093(term)

1557

msgid "--fatal-warnings"

1558

msgstr ""

1559

1560

#: C/gdm.xml:2095(para)

1561

msgid "Make all warnings cause GDM to exit."

1562

msgstr ""

1563

1564

#: C/gdm.xml:2102(term)

1565

msgid "--timed-exit"

1566

msgstr ""

1567

1568

#: C/gdm.xml:2104(para)

1569

msgid "Exit after 30 seconds. Useful for debugging."

1570

msgstr ""

1571

1572

#: C/gdm.xml:2111(term)

1573

msgid "--version"

1574

msgstr ""

1575

1576

#: C/gdm.xml:2113(para)

1577

msgid "Print the version of the GDM daemon."

1578

msgstr ""

1579

1580

#: C/gdm.xml:2122(title)

1581

msgid "<command>gdm-restart</command> Command Line Options"

1582

msgstr ""

1583

1584

#: C/gdm.xml:2124(para)

1585

msgid "<command>gdm-restart</command> stops and restarts GDM by sending the GDM daemon a HUP signal. This command will immediately terminate all sessions and log out users currently logged in with GDM."

1586

msgstr ""

1587

1588

#: C/gdm.xml:2132(title)

1589

msgid "<command>gdm-safe-restart</command> Command Line Options"

1590

msgstr ""

1591

1592

#: C/gdm.xml:2134(para)

1593

msgid "<command>gdm-safe-restart</command> stops and restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out."

1594

msgstr ""

1595

1596

#: C/gdm.xml:2142(title)

1597

msgid "<command>gdm-stop</command> Command Line Options"

1598

msgstr ""

1599

1600

#: C/gdm.xml:2144(para)

1601

msgid "<command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal."

1602

msgstr ""

1603

1604

#: C/gdm.xml:2155(title)

1605

msgid "Troubleshooting"

1606

msgstr ""

1607

1608

#. <para>

1609

#. TODO - any other tips we should add? Might be useful to highlight any

1610

#. common D-Bus configuration issues?

1611

#. </para>

1612

#: C/gdm.xml:2163(para)

1613

msgid "This section discusses helpful tips for getting GDM working. In general, if you have a problem using GDM, you can submit a bug or send an email to the gdm-list mailing list. Information about how to do this is in the Introduction section of the document."

1614

msgstr ""

1615

1616

#: C/gdm.xml:2170(para)

1617

msgid "If GDM is failing to work properly, it is always a good idea to include debug information. To enable debugging, set the debug/Enable key to \"true\" in the <filename><etc>/gdm/custom.conf</filename> file and restart GDM. Then use GDM to the point where it fails, and debug output will be sent to the system log file (<filename><var>/log/messages</filename> or <filename><var>/adm/messages</filename> depending on your Operating System). If you share this output with the GDM community via a bug report or email, please only include the GDM related debug information and not the entire file since it can be large. If you do not see any GDM syslog output, you may need to configure syslog (refer to the <ulink type=\"help\" url=\"man:syslog\">syslog</ulink> man page)."

1618

msgstr ""

1619

1620

#: C/gdm.xml:2186(title)

1621

msgid "GDM Will Not Start"

1622

msgstr ""

1623

1624

#: C/gdm.xml:2188(para)

1625

msgid "There are a many problems that can cause GDM to fail to start, but this section will discuss a few common problems and how to approach tracking down a problem with GDM starting. Some problems will cause GDM to respond with an error message or dialog when it tries to start, but it can be difficult to track down problems when GDM fails silently."

1626

msgstr ""

1627

1628

#: C/gdm.xml:2197(para)

1629

msgid "First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system."

1630

msgstr ""

1631

1632

#: C/gdm.xml:2210(para)

1633

msgid "Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start."

1634

msgstr ""

1635

1636

#: C/gdm.xml:2221(title)

1637

msgid "License"

1638

msgstr "Dovoljenje"

1639

1640

#: C/gdm.xml:2222(para)

1641

msgid "This program is free software; you can redistribute it and/or modify it under the terms of the <ulink type=\"help\" url=\"gnome-help:gpl\"><citetitle>GNU General Public License</citetitle></ulink> as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version."

1642

msgstr ""

1643

1644

#: C/gdm.xml:2230(para)

1645

msgid "This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <citetitle>GNU General Public License</citetitle> for more details."

1646

msgstr ""

1647

1648

#: C/gdm.xml:2236(para)

1649

msgid "A copy of the <citetitle>GNU General Public License</citetitle> is included as an appendix to the <citetitle>GNOME Users Guide</citetitle>. You may also obtain a copy of the <citetitle>GNU General Public License</citetitle> from the Free Software Foundation by visiting <ulink type=\"http\" url=\"http://www.fsf.org\">their Web site</ulink> or by writing to <address> Free Software Foundation, Inc. <street>51 Franklin Street, Fifth Floor</street><city>Boston</city>, <state>MA</state><postcode>02110-1301</postcode><country>USA</country></address>"

1650

msgstr ""

1651

1652

#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2

1653

#: C/gdm.xml:0(None)

1654

msgid "translator-credits"

1655

msgstr ""

1656