1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>
Tux Paint Frequently Asked Questions </title>
<meta http-equiv="Content-Type"
content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF"
text="#000000"
link="#0000FF"
vlink="#FF0000"
alink="#FF00FF">
<center>
<h1>
<img src="../../html/images/tuxpaint-title.png"
width="205"
height="210"
alt="Tux Paint"><br>
versión 0.9.28 Frequently Asked Questions </h1>
<p>
Copyright © 2002-2022 by various contributors; see <a href="../../AUTHORS.txt">AUTHORS.txt</a>.<br>
<a href="https://tuxpaint.org/">https://tuxpaint.org/</a>
</p>
<p>
junio 4, 2022 </p>
</center>
<hr size="2"
noshade>
<table border="2"
cellspacing="0"
cellpadding="2"
summary="Table of Contents">
<tr>
<th>
Table of Contents </th>
</tr>
<tr>
<td>
<ul>
<li>
<a href="#drawing">Drawing-related</a>
</li>
<li>
<a href="#interface">Interface Problems</a>
</li>
<li>
<a href="#printing">Printing</a>
</li>
<li>
<a href="#saving">Saving</a>
</li>
<li>
<a href="#audio">Audio Problems</a>
</li>
<li>
<a href="#fullscreen">Fullscreen Mode Problems</a>
</li>
<li>
<a href="#other">Other Probelms</a>
</li>
<li>
<a href="#contact">Help / Contact</a>
</li>
</ul>
</td>
</tr>
</table>
<hr size="2"
noshade>
<h2>
<a name="drawing" id="drawing">
Drawing-related </a>
</h2>
<dl>
<dt>
Fonts I added to Tux Paint only show squares </dt>
<dd>
The TrueType Font you're using might have the wrong encoding. If it's 'custom' encoded, for example, you can try running it through FontForge (<a href="http://fontforge.sourceforge.net/">http://fontforge.sourceforge.net/</a>) to convert it to an ISO-8859 format. (Email us if you need help with special fonts.) </dd>
<dt>
The Rubber Stamp tool is greyed out! </dt>
<dd>
<p>
This means that Tux Paint either couldn't find any stamp images, or was asked not to load them. </p>
<p>
If you installed Tux Paint, but did not install the separate, optional "Stamps" collection, quit Tux Paint and install it now. It should be available from the same place you got the main Tux Paint program. <i>(Note: As of version 0.9.14, Tux Paint comes with a small collection of example stamps.)</i> </p>
<p>
If you don't want to install the default collection of stamps, you can just create your own. See the "Extending Tux Paint" documentation for more on creating PNG and SVG image files, TXT text description files, Ogg Vorbis, MP3 or WAV sound files, and DAT text data files that make up stamps. </p>
<p>
Finally, if you installed stamps, and think they should be loading, check to see that the "nostamps" option isn't being set. (Either via a "<code>--nostamps</code>" option to Tux Paint's command line, or "<code>nostamps=yes</code>" in the configuration file.) </p>
<p>
Either change/remove the "nostamps" option, or you can override it with "<code>--stamps</code>" on the command line or either "<code>nostamps=no</code>" or "<code>stamps=yes</code>" in a configuration file. </p>
</dd>
<dt>
The "Fill" Tool Looks Bad </dt>
<dd>
<p>
Tux Paint is probably comparing exact pixel colors when filling. This is faster, but looks worse. Run the command "<code>tuxpaint --verbose-version</code>" from a command line, and you should see, amongst the other output: "Low Quality Flood Fill enabled". </p>
<p>
To change this, you must rebuild Tux Paint from source. Be sure to remove or comment out any line that says: </p>
<blockquote>
<p>
<code>#define LOW_QUALITY_FLOOD_FILL</code>
</p>
</blockquote>
<p>
in the "tuxpaint.c" file in the "src" directory. </p>
</dd>
<dt>
Stamp outlines are always rectangles </dt>
<dd>
<p>
Tux Paint was built with low-quality (but faster) stamp outlines. </p>
<p>
To change this, you must rebuild Tux Paint from source. Be sure to remove or comment out any line that says: </p>
<blockquote>
<p>
<code>#define LOW_QUALITY_STAMP_OUTLINE</code>
</p>
</blockquote>
<p>
in the "tuxpaint.c" file in the "src" directory. </p>
</dd>
</dl>
<hr size="2"
noshade>
<h2>
<a name="interface" id="interface">
Interface Problems </a>
</h2>
<dl>
<dt>
Stamp thumbnails in the Stamp Selector look bad </dt>
<dd>
<p>
Tux Paint was probably compiled with the faster, lower quality thumbnail code enabled. Run the command: "<code>tuxpaint --verbose-version</code>" from a command line. If, amongst the other output, you see the text: "Low Quality Thumbnails enabled", then this is what's happening. </p>
<p>
To change this, you must rebuild Tux Paint from source. Be sure to remove or comment out any line that says: </p>
<blockquote>
<p>
<code>#define LOW_QUALITY_THUMBNAILS</code>
</p>
</blockquote>
<p>
in the "tuxpaint.c" file in the "src" directory. </p>
</dd>
<dt>
Pictures in the 'Open' dialog look bad </dt>
<dd>
"Low Quality Thumbnails" is probably enabled. See: "Stamp thumbnails in the Stamp Selector look bad", above. </dd>
<dt>
The color picker buttons are ugly squares, not pretty buttons! </dt>
<dd>
<p>
Tux Paint was probably compiled with the nice looking color selector buttons disabled. Run the command: "<code>tuxpaint --verbose-version</code>" from a command line. If, amongst the other output, you see the text: "Low Quality Color Selector enabled", then this is what's happening. </p>
<p>
To change this, you must rebuild Tux Paint from source. Be sure to remove or comment out any line that says: </p>
<blockquote>
<p>
<code>#define LOW_QUALITY_COLOR_SELECTOR</code>
</p>
</blockquote>
<p>
in the "tuxpaint.c" file in the "src" directory. </p>
</dd>
<dt>
All of the text is in uppercase! </dt>
<dd>
<p>
The "uppercase" option is on. </p>
<p>
Either change/remove the "uppercase" option, or you can override it with "<code>--mixedcase</code>" on the command line or either "<code>uppercase=no</code>" or "<code>mixedcase=yes</code>" in a configuration file. </dd>
<dt>
Tux Paint is in a different language </dt>
<dd>
Make sure your locale setting is correct. See "Tux Paint won't switch to my language", below. </dd>
<dt>
Tux Paint won't switch to my language </dt>
<dd>
<ul>
<li>
<i>Linux and Unix users: Make sure the locale is available</i>
<p>
Make sure the locale you want is available. Check your "/etc/locale.gen" file. See the "Options Documentation" for the locales Tux Paint uses (especially when using the "<code>--lang</code>" option). </p>
<p>
Note: Debian and derivative (e.g., Ubuntu) users can simply run "<code>dpkg-reconfigure locales</code>" if the locales are managed by "dpkg". </p>
</li>
<li>If you're using the "<code>--lang</code>" command-line option <p>
Try using the "<code>--locale</code>" command-line option, or your operating system's locale settings (e.g., the "<code>$LANG</code>" environment variable), and please e-mail us regarding your trouble. </p>
</li>
<li>If you're using the "<code>--locale</code>" command-line option <p>
If this doesn't work, please e-mail us regarding your trouble. </p>
</li>
<li>If you're trying to use your Operating System's locale <p>
If this doesn't work, please e-mail us regarding your trouble. </p>
</li>
<li>Make sure you have the necessary font <p>
Some translations require their own font. Chinese and Korean, for example, need Chinese and Korean TrueType Fonts installed and placed in the proper location, respectively. </p>
<p>
The appropriate fonts for such locales can be downloaded from the Tux Paint website: </p>
<blockquote>
<p>
<a href=
"https://tuxpaint.org/download/fonts/">https://tuxpaint.org/download/fonts/</a>
</p>
</blockquote>
</li>
</ul>
</dd>
</dl>
<hr size="2"
noshade>
<h2>
<a name="printing" id="printing">
Printing </a>
</h2>
<dl>
<dt>
Tux Paint won't print, gives an error, or prints garbage (Unix/Linux) </dt>
<dd>
<p>
Tux Paint prints by creating a PostScript rendition of the picture and sending it to an external command. By default, this command is the "<code>lpr</code>" printing tool. </p>
<p>
If that program is not available (for example, you're using CUPS, the Common Unix Printing System, and do not have "<code>cups-lpr</code>" installed), you will need to specify an appropriate command using the "<code>printcommand</code>" option in Tux Paint's configuration file. (See the "Options Documentation".) </p>
<p>
<i>Note:</i> Versions of Tux Paint prior to 0.9.15 used a different default command for printing, "<code>pngtopnm | pnmtops | lpr</code>", as Tux Paint output PNG format, rather than PostScript. </p>
<p>
If you had changed your "printcommand" option prior to Tux Paint 0.9.15, you will need to go back and alter it to accept PostScript. </p>
</dd>
<dt>
I get the message "You can't print yet!" when I go to print </dt>
<dd>
<p>
The "print delay" option is on. You can only print once every <i>X</i> seconds. </p>
<p>
If you're running Tux Paint from a command-line, make sure you're not giving it a "<code>--printdelay=...</code>" option. </p>
<p>
If you're running Tux Paint by double-clicking an icon, check the properties of the icon to see if "<code>--printdelay=...</code>" is listed as a command-line argument. </p>
<p>
If a "<code>--printdelay=...</code>" option isn't being sent on the command line, check Tux Paint's configuration file for a line reading: "<code>printdelay=...</code>". </p>
<p>
Either remove that line, set the delay value to 0 (no delay), or decrease the delay to a value you prefer. (See the "Options Documentation".) </p>
<p>
Or, you can simply run Tux Paint with the command-line argument: "<code>--printdelay=0</code>", which will override the configuration file's setting, and allow unlimited printing. (You won't have to wait between prints.) </p>
</dd>
<dt>
I simply can't print! The button is greyed out! </dt>
<dd>
<p>
The "no print" option is on. </p>
<p>
If you're running Tux Paint from a command-line, make sure you're not giving it a "<code>--noprint</code>" option. </p>
<p>
If you're running Tux Paint by double-clicking an icon, check the properties of the icon to see if "<code>--noprint</code>" is listed as a command-line argument. </p>
<p>
If a "<code>--noprint</code>" option isn't being sent on the command line, check Tux Paint's configuration file for a line reading: "<code>noprint=yes</code>". </p>
<p>
Either remove that line, or simply run Tux Paint with the command-line argument: "<code>--print</code>", which will override the configuration file's setting. </p>
<p>
Or use Tux Paint Config. and make sure "Allow Printing" (under "Printing") is checked. </p>
</dd>
</dl>
<hr size="2"
noshade>
<h2>
<a name="saving" id="saving">
Saving </a>
</h2>
<dl>
<dt>
Where does Tux Paint save my drawings? </dt>
<dd>
<p>
Unless you asked Tux Paint to save into a specific location (using the "savedir" option), Tux Paint saves into a standard location on your local drive: </p>
<dl>
<dt>
Windows Vista, Windows 8, Windows 10, Windows 11
</dt>
<dd>
In the user's "AppData" folder:<br> e.g., <code>C:\Users\<i>Username</i>\AppData\Roaming\TuxPaint\saved</code> </dd>
<dt>
macOS
</dt>
<dd>
In the user's "Application Support" folder:<br> e.g., <code>/Users/<i>Username</i>/Library/Applicaton Support/TuxPaint/saved/</code> </dd>
<dt>
Linux / Unix
</dt>
<dd>
In the user's home directory ("<code>$HOME</code>"), under a ".tuxpaint" subfolder:<br> e.g., <code>/home/<i>username</i>/.tuxpaint/saved/</code> </dd>
</dl>
<p>
The images are stored as PNG bitmaps, which most modern programs should be able to load (image editors, word processors, web browsers, etc.) </p>
</dd>
<dt>
Tux Paint always saves over my old picture </dt>
<dd>
<p>
The "save over" option is enabled. (This disables the prompt that would appear when you click 'Save.') </p>
<p>
If you're running Tux Paint from a command-line, make sure you're not giving it a "<code>--saveover</code>" option. </p>
<p>
If you're running Tux Paint by double-clicking an icon, check the properties of the icon to see if "<code>--saveover</code>" is listed as a command-line argument. </p>
<p>
If a "--saveover" option isn't being sent on the command line, check Tux Paint's configuration file for a line reading: "saveover=yes". </p>
<p>
Either remove that line, or simply run Tux Paint with the command-line argument: "<code>--saveoverask</code>", which will override the configuration file's setting. </p>
<p>
Or use Tux Paint Config. and make sure "Ask Before Overwriting" (under "Saving") is checked. </p>
<p>
Also, see "Tux Paint always saves a new picture!", below. </p>
</dd>
<dt>
Tux Paint always saves a new picture! </dt>
<dd>
<p>
The "never save over" option is enabled. (This disables the prompt that would appear when you click 'Save.') </p>
<p>
If you're running Tux Paint from a command-line, make sure you're not giving it a "<code>--saveovernew</code>" option. </p>
<p>
If you're running Tux Paint by double-clicking an icon, check the properties of the icon to see if "<code>--saveovernew</code>" is listed as a command-line argument. </p>
<p>
If a "<code>--saveovernew</code>" option isn't being sent on the command line, check Tux Paint's configuration file for a line reading: "<code>saveover=new</code>". </p>
<p>
Either remove that line, or simply run Tux Paint with the command-line argument: "<code>--saveoverask</code>", which will override the configuration file's setting. </p>
<p>
Or use Tux Paint Config. and make sure "Ask Before Overwriting" (under "Saving") is checked. </p>
<p>
Also, see "Tux Paint always saves over my old picture!", above. </p>
</dd>
</dl>
<hr size="2"
noshade>
<h2>
<a name="audio" id="audio">
Audio Problems </a>
</h2>
<dl>
<dt>
There's no sound! </dt>
<dd>
<ul>
<li>
<em>First, check the obvious:</em>
<ul>
<li>Are your speakers connected and turned on?</li>
<li>Is the volume turned up on your speakers?</li>
<li>Is the volume turned up in your Operating System's "mixer?"</li>
<li>Are you certain you're using a computer with a sound card?</li>
<li>Are any other programs running that use sound? (They may be 'blocking' Tux Paint from accessing your sound device)</li>
<li>(Unix/Linux) Are you using a sound system, such as aRts, ESD or GStreamer? If so, try setting the "SDL_AUDIODRIVER" environment variable before running Tux Paint (e.g., "<code>export SDL_AUDIODRIVER=arts</code>"). Or, run Tux Paint through the system's rerouter (e.g., run "<code>artsdsp tuxpaint</code>" or "<code>esddsp tuxpaint</code>", instead of simply "<code>tuxpaint</code>"). </li>
</ul>
</li>
<li>
<em>Is sound disabled in Tux Paint?</em>
<p>
If sound seems to work otherwise (and you're sure no other program is "blocking" the sound device), then Tux Paint may be running with a "no sound" option. </p>
<p>
If you're running Tux Paint from a command-line, make sure you're not giving it a "--nosound" option. </p>
<p>
If you're running Tux Paint by double-clicking an icon, check the properties of the icon to see if "--nosound" is listed as a command-line argument. </p>
If a "<code>--nosound</code>" option isn't being sent on the command line, check Tux Paint's configuration file for a line reading: "<code>nosound=yes</code>". </p>
<p>
Either remove that line, or simply run Tux Paint with the command-line argument: "<code>--sound</code>", which will override the configuration file's setting. </p>
<p>
Or, you can simply run Tux Paint with the command-line argument: "Enable Sound Effects", which will override the configuration file's setting, and allow unlimited printing. (You won't have to wait between prints.) </p>
</li>
<li>
<em>Were sounds temporarily disabled?</em>
<p>
Even if sounds are enabled in Tux Paint, it is possible to disable and re-enable them temporarily using the <b>[Alt]</b> + <b>[S]</b> key sequence. Try pressing those keys to see if sounds begin working again. </p>
</li>
<li>
<em>Was Tux Paint built without sound support?</em>
<p>
Tux Paint may have been compiled with sound support disabled. To test whether sound support was enabled when Tux Paint was compiled, run Tux Paint from a command line, like so: </p>
<blockquote>
<p>
<code>tuxpaint --verbose-version</code>
</p>
</blockquote>
<p>
If, amongst the other information, you see "Sound disabled", then the version of Tux Paint you're running has sound disabled. Recompile Tux Paint, and be sure NOT to build the "nosound" target. (i.e., don't run "<code>make nosound</code>") Be sure the SDL_mixer library and its development headers are available! </p>
</li>
</ul>
</dd>
<dt>
Tux Paint makes too much noise! Can I turn them off? </dt>
<dd>
<p>
Yes, there are a number of ways to disable sounds in Tux Paint: </p>
<ul>
<li>Press <b>[Alt]</b> + <b>[S]</b> while in Tux Paint to temporarily disable sounds. (Press that key sequence again to re-enable sounds.) </li>
<li>Run Tux Paint with the "no sound" option: <ul>
<li>Run "<code>tuxpaint --nosound</code>" from the command line or shortcut or desktop icon. </li>
<li>Edit Tux Paint's configuration file (see "Options Documentation" for details) and add a line containing "<code>nosound=yes</code>". </li>
<li>
Or use Tux Paint Config. and make sure "Enable Sound Effects" (under "Video & Sound") is not checked. </li>
<li>
Alternatively, recompile Tux Paint with sound support disabled. (See above, and the 'Install' documentation. </li>
</ul>
</li>
</ul>
</dd>
<dt>
The stereo panning of sound effects is bothersome; can sound effects be monophonic? </dt>
<dd>
<p>
Run Tux Paint with the "no stereo" option: </p>
<ul>
<li>Run "<code>tuxpaint --nostereo</code>" from the command line or shortcut or desktop icon. </li>
<li>Edit Tux Paint's configuration file (see "Options Documentation" for details) and add a line containing "<code>nostereo=yes</code>". </li>
<li>
Or use Tux Paint Config. and make sure "Enable Stereo Effects" (under "Video & Sound") is not checked. </li>
</ul>
</dd>
<dt>
The sound effects sound strange </dt>
<dd>
<p>
This could have to do with how SDL and SDL_mixer were initialized. (The buffer size chosen.) </p>
<p>
Please e-mail us with details about your computer system. (Operating system and version, sound card, which version of Tux Paint you're running (run "<code>tuxpaint --version</code>" to verify), and so on.) </p>
</dd>
</dl>
<hr size="2"
noshade>
<h2>
<a name="fullscreen" id="fullscreen">
Fullscreen Mode Problems </a>
</h2>
<dl>
<dt>
When I run Tux Paint full-screen and <b>[Alt]</b> + <b>[Tab]</b> out, the window turns black! </dt>
<dd>
This is apparently a bug in the SDL library. Sorry. </dd>
<dt>
When I run Tux Paint full-screen, it has large borders around it </dt>
<dd>
<p>
Linux users - Your X-Window server is probably not set with the ability to switch to the desired resolution: 800×600. (or whatever resolution you have Tux Paint set to run at.) (This is typically done manually under the X-Window server by pressing <span style="white-space: nowrap;"><b><code>[Control]</code></b> + <b><code>[Alt]</code></b> + <b><code>[<span style="white-space: nowrap;">Keypad Plus (+)</span>]</code></b></span> and <span style="white-space: nowrap;"><b><code>[Control]</code></b> + <b><code>[Alt]</code></b> + <b><code>[<span style="white-space: nowrap;">Keypad Minus (-)</span>]</code></b></span>.) </p>
<p>
For this to work, your monitor must support that resolution, and you need to have it listed in your X server configuration. </p>
<p>
Check the "Display" subsection of the "Screen" section of your XFree86 or X.org configuration file (typically "<code>/etc/X11/XF86Config-4</code>" or "<code>/etc/X11/XF86Config</code>", depending on the version of XFree86 you're using; 3.x or 4.x, respectively, or "<code>/etc/X11/xorg.conf</code>" for X.org). </p>
<p>
Add "<code>800x600</code>" (or whatever resolution(s) you want) to the appropriate "Modes" line. (e.g., in the "Display" subsection that contains 24-bit color depth ("Depth 24"), which is what Tux Paint tries to use.) </p>
<blockquote>
<p>
<code>Modes "1280x1024" "1024x768" "800x600" "640x480"</code>
</p>
</blockquote>
<p>
Note that some Linux distributions have tools that can make these changes for you. Debian users can run the command "<code>dpkg-reconfigure xserver-xfree86</code>" as root, for example. </p>
</dd>
<dt>
Tux Paint keeps running in Full Screen mode - I want it windowed! </dt>
<dd>
<p>
The "fullscreen" option is set. </p>
<p>
If you're running Tux Paint from a command-line, make sure you're not giving it a "<code>--fullscreen</code>" option. </p>
<p>
If you're running Tux Paint by double-clicking an icon, check the properties of the icon to see if "<code>--fullscreen</code>" is listed as a command-line argument. </p>
<p>
If a "<code>--fullscreen</code>" option isn't being sent on the command line, check Tux Paint's configuration file for a line reading: "<code>fullscreen=yes</code>". </p>
<p>
Either remove that line, or simply run Tux Paint with the command-line argument: "<code>--windowed</code>", which will override the configuration file's setting. </p>
<p>
Or use Tux Paint Config. and make sure "Fullscreen" (under "Video & Sound") is not checked. </p>
</dd>
</dl>
<hr size="2"
noshade>
<h2>
<a name="other" id="other">
Other Probelms </a>
</h2>
<dl>
<dt>
Tux Paint won't run </dt>
<dd>
<p>
If Tux Paint aborts with the message: "You're already running a copy of Tux Paint!", this means it has been launched in the last 30 seconds. (On Unix/Linux, this message would appear in a terminal console if you ran Tux Paint from a command-line. On Windows, this message would appear in a file named "<code>stdout.txt</code>" in the same folder where <code>TuxPaint.exe</code> resides (e.g., in "<code>C:\Program Files\TuxPaint</code>"). </p>
<p>
A lockfile ("~/.tuxpaint/lockfile.dat" on Linux and Unix, "userdata\lockfile.dat" on Windows) is used to make sure Tux Paint isn't run too many times at once (e.g., due to a child impatiently clicking its icon more than once). </p>
<p>
Even if the lockfile exists, it contains the 'time' Tux Paint was last run. If it's been more than 30 seconds, Tux Paint should run fine, and simply update the lockfile with the current time. </p>
<p>
If multiple users are sharing the directory where this file is stored (e.g., on a shared network drive), then you'll need to disable this feature. </p>
<p>
To disable the lockfile, add the "<code>--nolockfile</code>" argument to Tux Paint's command-line, or "<code>nolockfile=yes</code>" to the configuration file. </p>
</dd>
<dt>
I can't quit Tux Paint </dt>
<dd>
<p>
The "no quit" option is set. This disables the "Quit" button in Tux Paint's toolbar (greying it out), and prevents Tux Paint from being exited via the <b>[Escape]</b> key. </p>
<p>
If Tux Paint is not in fullscreen mode, simply click the window close button on Tux Paint's title bar. (i.e., the "ⓧ" at the upper right.) </p>
<p>
If Tux Paint is in fullscreen mode, you will need to use the <b>[Shift]</b> + <b>[Control]</b> + <b>[Escape]</b> sequence on the keyboard to quit Tux Paint. </p>
<p>
(Note: with or without "no quit" set, you can always use the <b>[Alt]</b> + <b>[F4]</b> combination on your keyboard to quit Tux Paint.) </p>
</dd>
<dt>
I don't want "no quit" mode enabled! </dt>
<dd>
<p>
If you're running Tux Paint from a command-line, make sure you're not giving it a "--noquit" option. </p>
<p>
If you're running Tux Paint by double-clicking an icon, check the properties of the icon to see if "<code>--noquit</code>" is listed as a command-line argument. </p>
<p>
If a "<code>--noquit</code>" option isn't being sent on the command line, check Tux Paint's configuration file for a line reading: "<code>noquit=yes</code>". </p>
<p>
Either remove that line, or simply run Tux Paint with the command-line argument: "<code>--quit</code>", which will override the configuration file's setting. </p>
<p>
Or use Tux Paint Config. and make sure "Disable Quit Button and [Escape] Key" (under "Simplification") is not checked. </p>
</dd>
<dt>
Tux Paint keeps writing weird messages to the screen / to a text file </dt>
<dd>
<p>
A few messages are normal, but if Tux Paint is being extremely verbose (like listing the name of every rubber-stamp image it finds while loading them), then it was probably compiled with debugging output turned on. </p>
<p>
To change this, you must rebuild Tux Paint from source. Be sure to remove or comment out any line that says: </p>
<blockquote>
<p>
<code>#define DEBUG</code>
</p>
</blockquote>
<p>
in the "tuxpaint.c" file in the "src" directory. </p>
</dd>
<dt>
Tux Paint is using options I didn't specify! </dt>
<dd>
<p>
By default, Tux Paint first looks at configuration files for options. </p>
<ul>
<li>
<i>Unix and Linux</i>
<p>
Under Unix and Linux, it first examines the system-wide configuration file, located here: </p>
<blockquote>
<p>
<code>/etc/tuxpaint/tuxpaint.conf</code>
</p>
</blockquote>
<p>
It then examines the user's personal configuration file: </p>
<blockquote>
<p>
<code>~/.tuxpaintrc</code>
</p>
</blockquote>
<p>
Finally, any options sent as command-line arguments are used. </p>
</li>
<li>
<i>Windows</i>
<p>
Under Windows, Tux Paint first examines the configuration file: </p>
<blockquote>
<p>
<code>tuxpaint.cfg</code>
</p>
</blockquote>
<p>
Finally, any options sent as command-line arguments are used. </p>
</li>
</ul>
<p>
This means that if anything is set in a configuration file that you don't want set, you'll need to either change the config. file (if you can), or override the option on the command-line. </p>
<p>
For example, on Linux and Unix, if "/etc/tuxpaint/tuxpaint.conf" includes this option to disable sound... </p>
<blockquote>
<p>
<code>nosound=yes</code>
</p>
</blockquote>
<p>
...then you can reenable sound by either adding this option to your own ".tuxpaintrc" file: </p>
<blockquote>
<p>
<code>sound=yes</code>
</p>
</blockquote>
<p>
...or by using this command-line argument: </p>
<blockquote>
<p>
<code>--sound</code>
</p>
</blockquote>
<p>
Linux and Unix users can also disable the system-wide configuration file by including the following command-line argument: </p>
<blockquote>
<p>
<code>--nosysconfig</code>
</p>
</blockquote>
<p>
Tux Paint will then only look at "~/.tuxpaintrc" and command-line arguments to determine what options should be set. </p>
</dd>
</dl>
<hr size="2"
noshade>
<h2>
<a name="contact" id="contact">
Help / Contact </a>
</h2>
<p>
Any questions you don't see answered? Please let us know! You can subscribe and post to our "tuxpaint-users" mailing list: </p>
<blockquote>
<p>
<a href="https://tuxpaint.org/lists/">https://tuxpaint.org/lists/</a>
</p>
</blockquote>
<p>
Or, contact lead developer Bill Kendrick directly: </p>
<blockquote>
<p>
<a href=
"mailto:bill@newbreedsoftware.com">bill@newbreedsoftware.com</a>
</p>
</blockquote>
</body>
</html>
|
