Debian Bug report logs - #740
xserver-xfree86: xclock leaves 'droppings' in its window

Toggle useless messages

Message #29 received at 740@bugs.debian.org (full text, mbox, reply):

From: Stephen Early <steve@myrddin.greenend.org.uk>

To: ian@chiark.greenend.org.uk, 740@bugs.debian.org

Subject: Debian bug#740

Date: Sun, 10 Nov 96 00:33 GMT

(this is one of the oldest Debian bugs; it's about display corruption
in your X server)

Could you tell me whether you still have the problem described in this
bug report?

Steve

Message #34 received at 740@bugs.debian.org (full text, mbox, reply):

From: Ian Jackson <ian@chiark.greenend.org.uk>

To: 740@bugs.debian.org

Subject: Bug#740: xclock leaves `droppings' in its window

Date: Wed, 13 Nov 96 02:35 GMT

Yes, I've had this problem recently with xserver-s3 3.1.2-5.  I've
also, btw, seen it happen on the Cockroft 4 Pentiums here in
Cambridge, when running the 3.1.2 XF86_S3 that's in Mond Linux.

Ian.

Message #39 received at 740@bugs.debian.org (full text, mbox, reply):

From: Guy Maor <maor@ece.utexas.edu>

To: 740@bugs.debian.org

Subject: Re: Bug#740: xclock leaves `droppings' in its window

Date: 13 Nov 1996 01:03:41 -0600

Ian Jackson <ian@chiark.greenend.org.uk> writes:

> Yes, I've had this problem recently with xserver-s3 3.1.2-5.  I've
> also, btw, seen it happen on the Cockroft 4 Pentiums here in
> Cambridge, when running the 3.1.2 XF86_S3 that's in Mond Linux.

Just so it doesn't seem like Ian's in his own little world, I'll add
that I've seen it too, a while back on xserver-mach32 3.1.2-5.

I haven't seen it with newer beta xservers - I never run xclock
anymore since the watch on my wrist consumes 1 meg less resident
memory.


Guy

Message #44 received at 740@bugs.debian.org (full text, mbox, reply):

From: bmbuck@acsu.buffalo.edu

To: 740@bugs.debian.org

Subject: Xclock droppings bug is back

Date: Fri, 20 Jun 1997 23:27:18 -0400

Greetings,

This is the second oldest outstanding bug in the bug database, and it 
appears to be back.  Ever since I upgraded to XFree86 3.3, Xclock has 
been leaving "droppings" in its window.

I'm using XFree86 3.3-2, the xserver-svga 3.3-2 server, fvwm2 
2.0.45-BETA-4, fvwm-common 2.0.45-BETA-4.

My video mode is 1024x768, I'm using the Cirrus chipset, and I am using 
a grey background inside the xclock.  A gif can be made available upon 
request.

Hope this helps!

-- 
     Buddha Buck                      bmbuck@acsu.buffalo.edu
"Just as the strength of the Internet is chaos, so the strength of our
liberty depends upon the chaos and cacaphony of the unfettered speech
the First Amendment protects."  -- A.L.A. v. U.S. Dept. of Justice

Message #49 received at 740@bugs.debian.org (full text, mbox, reply):

From: mbaker@iee.org (Mark Baker)

To: bmbuck@acsu.buffalo.edu, 740@bugs.debian.org

Subject: Re: Bug#740: Xclock droppings bug is back

Date: Sat, 21 Jun 1997 10:19:20 +0100

In article <"bhia4.0.px6.q7sgp"@debian>,
	bmbuck@acsu.buffalo.edu writes:

> This is the second oldest outstanding bug in the bug database, and it 
> appears to be back.  Ever since I upgraded to XFree86 3.3, Xclock has 
> been leaving "droppings" in its window.
> 
> I'm using XFree86 3.3-2, the xserver-svga 3.3-2 server, fvwm2 
> 2.0.45-BETA-4, fvwm-common 2.0.45-BETA-4.
> 
> My video mode is 1024x768, I'm using the Cirrus chipset, and I am using 
> a grey background inside the xclock.  A gif can be made available upon 
> request.

I'm running exactly the same versions of all those, also on a Cirrus
graphics card at 1024x768, and I've never seen XClock leave droppings.
.

Message #54 received at 740@bugs.debian.org (full text, mbox, reply):

From: eichin@kitten.gen.ma.us (Mark W. Eichin)

To: mbaker@iee.org (Mark Baker)

Cc: 740@bugs.debian.org, bmbuck@acsu.buffalo.edu

Subject: Re: Bug#740: Xclock droppings bug is back

Date: 21 Jun 1997 11:07:14 -0400

Actually, what neither of you have mentioned is what CPU (and FPU if
relevant) you're using.  If it's the bug I think it is (the droppings
are from the "hands" of the clock, right?) usually it's a floating
point problem.

If you can put a gif up somewhere and send in a URL as part of the bug
report, that would be convenient (or if it's less than 10K I suppose
you could just uuencode it and send it directly...)

Message #59 received at 740@bugs.debian.org (full text, mbox, reply):

From: owner@bugs.debian.org (Ian Jackson)

To: 740@bugs.debian.org

Subject: Bug#740: Info received (was Bug#740: Xclock droppings bug is back)

Date: Sat, 21 Jun 97 08:18 PDT

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.

Your message has been sent to the package maintainer(s):
 eichin@kitten.gen.ma.us (Mark W. Eichin)

If you wish to continue to submit further information on your problem,
please send it to 740@bugs.debian.org, as before.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, Debian bug tracking system)

Message #64 received at 740@bugs.debian.org (full text, mbox, reply):

From: rjs@lloke.dna.fi (Riku Saikkonen)

To: 740@bugs.debian.org

Cc: bmbuck@acsu.buffalo.edu

Subject: The xclock droppings bug (#740)

Date: Sat, 12 Jul 1997 16:03:52 +0300

Just FYI, I've never seen this bug, though I've used X packages from 3.1.2-1
to 3.3-3, display adaters from Cirrus 5428 through S3-Trio64 to a Tseng
ET600, and of CPUs an Intel Pentium-100 and an AMD P5-133.

To someone who still sees this bug (does anyone?): Can you reproduce it
reasonably consistently? Does "xclock -update 1" provoke the bug faster
(i.e., does the second hand also leave droppings)? Does the bug occur only
at certain sizes of the xclock window? Have you noticed other applications
leaving some kind of droppings?

This seems to be a really strange bug. Xclock calls XDrawLines() to draw the
outlines of the hands and XFillPolygon() to fill in the centre, and to erase
an old hand, it should always call the same functions with the same set of
points but with a different GC. Apparently the erasing doesn't always happen
for some reason. From the screen shots, it looks like they aren't just
single-pixel droppings; sometimes big parts of the hands are dropped behind
(this would imply that it probably isn't a floating point calculation
problem).

The bug seems to be in XFree86's server implementation, but it's very
obscure.

--
-=- Rjs -=- rjs@spider.compart.fi, rjs@lloke.dna.fi

Message #69 received at 740@bugs.debian.org (full text, mbox, reply):

From: Richard Kaszeta <kaszeta@me.umn.edu>

To: rjs@isil.lloke.dna.fi, 740@bugs.debian.org

Cc: 740@bugs.debian.org, bmbuck@acsu.buffalo.edu

Subject: Re: Bug#740: The xclock droppings bug (#740)

Date: Sat, 12 Jul 1997 14:57:27 -0500

>To someone who still sees this bug (does anyone?): Can you reproduce it
>reasonably consistently? Does "xclock -update 1" provoke the bug faster
>(i.e., does the second hand also leave droppings)? Does the bug occur only
>at certain sizes of the xclock window? Have you noticed other applications
>leaving some kind of droppings?

I have een 'xclock' do droppings, and I have seen 'xarclock'
and 'swisswatch' leave them too.  'xclock -update 1' does it---after a
while the "diamond" for the second hand starts leaving artifacts.  A
forced redraw erases these, but if I don't redraw, I *can* capture it
with 'xv', so it's not videocard artifacts.

-- 
Richard W Kaszeta 			Graduate Student/Sysadmin
bofh@bofh.me.umn.edu			University of MN, ME Dept
http://www.menet.umn.edu/~kaszeta

Message #74 received at 740-maintonly@bugs.debian.org (full text, mbox, reply):

From: remco@blaakmeer.student.utwente.nl (Remco Blaakmeer)

To: 740-maintonly@bugs.debian.org

Subject: Old bugs need to be looked at

Date: Sun, 1 Feb 1998 11:59:52 +0100 (CET)

This is an automated message sent to all bugs older than one year.

This bug is very old. Please take a look at it and see if you can fix it.
If it has already been fixed, please close it.

If you have problems fixing it or if you don't have the time to fix it,
please ask the people on debian-devel@lists.debian.org for help, so that
at least the oldest bugs can be solved before Debian 2.0 is released.

Remco Blaakmeer

Message #79 received at 740@bugs.debian.org (full text, mbox, reply):

From: Remco Blaakmeer <remco@blaakmeer.student.utwente.nl>

To: 740@bugs.debian.org

Cc: sr1@irz301.inf.tu-dresden.de, maor@ece.utexas.edu, bmbuck@acsu.buffalo.edu, mbaker@iee.org, eichin@kitten.gen.ma.us, rjs@lloke.dna.fi, kaszeta@me.umn.edu, debian-devel@lists.debian.org

Subject: Re: Bug#740: The xclock droppings bug (#740)

Date: Wed, 4 Feb 1998 16:53:01 +0100 (CET)

This message is sent to bug#740, everybody who sent a message to that
bug report and the debian-devel mailinglist. For details about this bug,
please see http://www.debian.org/Bugs/db/74/740.html . I am sorry if it
bothers you that I Cc:'ed to everybody that has contributed to this bug
report. You are free to ignore this message if it bothers you.

In the bug report, Ian Jackson explains that xclock leaves 'droppings'.

Apart from my nag the other day, the last message to this bug is dated
July 12th, 1997. Can anyone still reproduce this bug with X version
3.3.1-2? If not, this bug should probably be closed.

I haven't been able to reproduce this bug, using:
- xbase, xlib6, xlib6g, xserver-s3: version 3.3.1-2
- libc6: version 2.0.6-3
- kernel: 2.0.33, no FPU emulation
- CPU: Intel P75
- video card: Diamond Stealth, using Vision868 chip

If anyone does find droppings, please supply relevant information like:
- which version of the xbase and xlib6/xlib6g packages you use
- which Xserveer you use (name and version)
- which video card you have
- which kernel you are using (self-compiled or Debian, FPU emulation?)
- which libc version have
- which kind of CPU you have (as detailed as possible, because this 'bug'
  could be caused by FPU errors)
- the exact command you start xclock with, including all parameters and
  switches
- versions of other important things I probably have forgotten

Please send any report on such droppings at least to 740@bugs.debian.org.
Plesae do not use 'reply to all' on this message.

If these droppings only happen on certain video cards it might be a
problem in one of the video card drivers. In that case, it might be a good
idea to forward this bug to the upstream authors.

Remco

Message #84 received at 740@bugs.debian.org (full text, mbox, reply):

From: James A. Treacy <treacy@debian.org>

To: 740@bugs.debian.org

Subject: Re: Bug#740: The xclock droppings bug (#740)

Date: Wed, 4 Feb 1998 11:27:35 -0500 (EST)

I still notice this problem from time to time. Usually when I return to
X after having switched to a VC for a while.

 - xbase, xlib6, xlib6g, xserver-mach64: version 3.3.1-2
 - libc6: version 2.0.6-3
 - kernel: 2.0.32, no FPU emulation
 - CPU: Intel P133
 - video card: ATI Mach 64 (CT)

This problem has been steady through all kernels and versions of X (always
using mach64 server) that I've used over the last 1.5 years.

- Jay

Message #89 received at 740@bugs.debian.org (full text, mbox, reply):

From: Jeff Sheinberg <jeffsh@erols.com>

To: 740@bugs.debian.org

Subject: Re: Bug#740: The xclock droppings bug (#740)

Date: Wed, 4 Feb 1998 17:28:03 -0500 (EST)

Remco Blaakmeer writes:
 > In the bug report, Ian Jackson explains that xclock leaves 'droppings'.
[snip]
 > - video card: Diamond Stealth, using Vision868 chip

I have been able to get `droppings' from my Diamond Stealth 64 Video VRAM
using the `fast vram' option in my XF86Config file.  The drops fall in
an xterm window.  The /usr/bin/clear command makes them go away
temporarily.  The video board has 2Mb -70ns edo vram.  I removed all
options pertaining to fast, slow, etc vram and the droppings disappeared
for good.

Here's the section from my XF86Config file.

    Section "Device"
       Identifier      "Diamond Stealth 64 Video VRAM"
       VendorName      "Diamond Multimedia Systems, Inc."
       BoardName       "Diamond Stealth64 Video 3240/3400 (IBM RAMDAC)"
       Chipset         "newmmio"
    ## Chipset "mmio_928"
       VideoRam         4096
    ## VideoRam 2048
       Ramdac          "ibm_rgb526"
       DacSpeed         220
       ClockChip       "ibm_rgb5xx"
    ## S3MClk   66.476
       S3RefClk         14.318
       Option          "power_saver"
    EndSection

As you can see, I've upgraded to 4MB vram.  Upon reviewing the above
XF86Config section, I'm pretty sure that the problem occurred using my
old commented out 2Mb configuration, since that's why I even considered
looking at the upgrade memory, which is, BTW, -60ns edo vram.

HTH,

-- 
Jeff Sheinberg  <jeffsh@erols.com>

Message #92 received at 740-quiet@bugs.debian.org (full text, mbox, reply):

From: Branden Robinson <branden@purdue.edu>

To: 740-quiet@bugs.debian.org

Subject: messed up screen refresh in X

Date: Wed, 15 Apr 1998 22:36:51 -0500

I too have seen this behavior, particularly when switching back to X
from a VC (for instance, to some fast-drawing mode of xlockmore -- stray
pixels are sometimes left on the screen).  My undereducated guess is
that it has something to do with the way the X servers acknowledge a
refresh request.  But I really don't know enough about this level of
Xlib to venture any further.

-- 
G. Branden Robinson                 |  It was a typical net.exercise -- a
Purdue University                   |  screaming mob pounding on a greasy spot
branden@purdue.edu                  |  on the pavement, where used to lie the
http://www.ecn.purdue.edu/~branden/ |  carcass of a dead horse.

Message #99 received at 740@bugs.debian.org (full text, mbox, reply):

From: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>

To: 740@bugs.debian.org, debian-user@lists.debian.org

Subject: Let's hunt the oldest bug!

Date: Sun, 8 Nov 1998 13:12:00 +0100

[Message part 1 (text/plain, inline)]

+---------------------------------------------------------------------+
| You don't have the time or experience to become a Debian developer? |
| Nevertheless you want to help?                                      |
|  or                                                                 |
| You are a hacker, longing for a task that is up to your abilities?  |
+---------------------------------------------------------------------+
|                    H U N T   T H E   B U G !                        |
+---------------------------------------------------------------------+
| A few minutes of your time can already help!                        |
+---------------------------------------------------------------------+

Hello,

Bug #740 is the oldest open bug report in the Debian archive.
We have two options:

1) Leave it there, as a symbol of the eternity of our Bug Tracking System, or
2) Hunt it, localize it, fix it.

Although 1) is very tempting, I thought we could at least try to find a
reliable way to reproduce the bug, so we can forward it upstream.

Background information:

Some people report that xclock leaves "droppings" in the window, this
means, the handles are not deleted correctly, some pixel remain.

Possible causes of the problem:

XClock callls XDrawLines() and XFillPolygon() to update the handles twice,
both times with the very same arguments, so the bug seems to be hidden in
the X libraries and/or servers or even in the FPU unit of the processor.

If anyone does find droppings, please supply relevant information like:
- which version of the xbase and xlib6/xlib6g packages you use
- which Xserver you use (name and version)
- how the Xserver is configured in /etc/X11/XF86Config (FastRam activated? etc)
- which video card you have and how fast the memory is (70 or 60ns?)
- which kernel you are using (self-compiled or Debian, FPU emulation?)
- which libc version have
- which kind of CPU you have (as detailed as possible, because this 'bug'
  could be caused by FPU errors)
- the exact command you start xclock with, including all parameters and
  switches
- versions of other important things I probably have forgotten


+-----------------------------------------------------------------------+
| Please run the attached `fastclock' binary, it is an `optimized'      |
| version of xclock, which runs about 60 times faster than the original.|
| As I have never seen droppings, I can't tell you how long you have to |
| run the program. If you see artifacts, please submit the information  |
| above to 740@bugs.debian.org                                          |
+-----------------------------------------------------------------------+

Thank you for your help,
Marcus


-- 
"Rhubarb is no Egyptian god."        Debian GNU/Linux        finger brinkmd@ 
Marcus Brinkmann                   http://www.debian.org    master.debian.org
Marcus.Brinkmann@ruhr-uni-bochum.de                        for public  PGP Key
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/       PGP Key ID 36E7CD09

[fastclock (application/octet-stream, attachment)]

Message #104 received at 740@bugs.debian.org (full text, mbox, reply):

From: James Dietrich <jdietrch@southern.edu>

To: 740@bugs.debian.org

Subject: droppings in xclock

Date: Wed, 11 Nov 1998 17:51:53 -0500

I ran xclock today and noted droppings.

At first, the only sequence of events that I found that would cause the
droppings, was to be in a VT while an update of any sort took place
and then return to X after the update occurred.  I've used 'xclock &'
and 'xclock -update 1 &' and 'fastclock &' (the attached binary from Marcus
in the previous email) with similar results.  The droppings occur either
at the update while I am in the VT or at the next update after returning
to X or both.  More specifically, switching out to a VT for a few seconds
nearly always causes the "second hand" in 'xclock -update 1 &' to drop one or
more pixels, and being in the VT over an update of the minute hand does
the same for that hand.  Apparently it is the trailing edge that is
"dropped" since with 'xclock -highlight green &' the droppings are green
and with 'xclock -hands red &' the droppings are black.

However, almost by accident I discovered that simply covering the xclock
window with something else will produce the same effect.  My window 
manager at the moment is Enlightenment, with the default configuration,
and when one of the huge :) tooltips covers a hand during an update, droppings
are left in the very same way as switching to a VT, as far as I can tell.
Also, the same result can be obtained by covering xclock with an xterm
window temporarily.  And only the portion of the hand covered will drop
pixels.  Furthermore, covering a hand and letting it come out from under
the covering on its own causes no dropping.

I've also noted that very quickly moving the xclock window around the
screen in X so that the virtual desktop is forced to move rapidly erases
the droppings in the window I am moving, but not any others that happen to
be on the desktop.  Also, I left 'xclock &' running for several hours
without covering it or switching to a VT and no droppings appeared.  So it
doesn't appear to be a matter of length of time running.  Also, most of
the time the "droppings" are one or more (sometimes many) pixels.  Usually
they are single pixels, but sometimes there are short lines, too--perhaps
simply a "concatenation" of dropped pixels in a line.

If I can be of any further help in solving this bug, I'll be glad to provide
more information and/or do further tests, etc.

HTH,

James


Relevant system info:
xbase: 3.3.2.3a-1
xlib6: none
xlib6g: 3.3.2.3a-1
xserver-mach64: 3.3.2.3a-1
video card: output of SuperProbe (I don't know how fast my video memory is)
First video: Super-VGA
        Chipset: ATI 264CT (Port Probed)
        Memory:  2048 Kbytes
        RAMDAC:  ATI Mach64 integrated 15/16/24/32-bit DAC w/clock
                 (with 6-bit wide lookup tables (or in 6-bit mode))
                 (programmable for 6/8-bit wide lookup tables)
        Attached graphics coprocessor:
                Chipset: ATI Mach64
                Memory:  2048 Kbytes
kernel: 2.1.126--self-compiled, no FPU emulation
libc6: 2.0.7u-4
CPU: cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 5
model           : 6
model name      : K6 (PR166 - PR266)
stepping        : 2
fdiv_bug        : no
hlt_bug         : no
sep_bug         : no
f00f_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 mmx
bogomips        : 333.41

Message #109 received at 740@bugs.debian.org (full text, mbox, reply):

From: alexander.schwartz@gmx.net

To: 740@bugs.debian.org

Subject: Re: Let's hunt the oldest bug!

Date: Fri, 13 Nov 1998 22:30:09 +0000 (GMT)

[Message part 1 (text/plain, inline)]

Ok, I have some drop outs (on the xclock in my Fvwm95TaskBar. So, what am
I supposed to do now? Here ist some data:

xbase        3.3.2.3-2
xserver-mach64 3.3.2.3-2 (XF86Config attached)
xlib6g       3.3.2.3-2
Video Card: ATI Mach3D Card (Mach64: PCI: Mach64 RageII+DVD rev 154,
Aperture @ 0xe2000000, Registers @ 0xe0800000, Block I/O @ 0xb400)
a standard debian kernel (2.0.34), config attached
libc6        2.0.7u-4

I start the xclock as follows in system.fvwm95rc (complete file attached)
*DebianFvwm95Buttons(Title xclock, Icon clock.xpm, \                
     Swallow(UseOld) "xclock" 'Exec /usr/bin/X11/xclock -bg \#c0c0c0 \
     -padding 0 -geometry -1500-1500 &')

I have a Pentium II 266 with 128 MB Ram, 
I don't know why XFree86 reports a 2.0.35 kernel.

I also attached the output of XFree

If there are any open questions, ask me.

Alex.

On Sun, 8 Nov 1998, Marcus Brinkmann wrote:

> 
> +---------------------------------------------------------------------+
> | You don't have the time or experience to become a Debian developer? |
> | Nevertheless you want to help?                                      |
> |  or                                                                 |
> | You are a hacker, longing for a task that is up to your abilities?  |
> +---------------------------------------------------------------------+
> |                    H U N T   T H E   B U G !                        |
> +---------------------------------------------------------------------+
> | A few minutes of your time can already help!                        |
> +---------------------------------------------------------------------+
> 
> Hello,
> 
> Bug #740 is the oldest open bug report in the Debian archive.
> We have two options:
> 
> 1) Leave it there, as a symbol of the eternity of our Bug Tracking System, or
> 2) Hunt it, localize it, fix it.
> 
> Although 1) is very tempting, I thought we could at least try to find a
> reliable way to reproduce the bug, so we can forward it upstream.
> 
> Background information:
> 
> Some people report that xclock leaves "droppings" in the window, this
> means, the handles are not deleted correctly, some pixel remain.
> 
> Possible causes of the problem:
> 
> XClock callls XDrawLines() and XFillPolygon() to update the handles twice,
> both times with the very same arguments, so the bug seems to be hidden in
> the X libraries and/or servers or even in the FPU unit of the processor.
> 
> If anyone does find droppings, please supply relevant information like:
> - which version of the xbase and xlib6/xlib6g packages you use
> - which Xserver you use (name and version)
> - how the Xserver is configured in /etc/X11/XF86Config (FastRam activated? etc)
> - which video card you have and how fast the memory is (70 or 60ns?)
> - which kernel you are using (self-compiled or Debian, FPU emulation?)
> - which libc version have
> - which kind of CPU you have (as detailed as possible, because this 'bug'
>   could be caused by FPU errors)
> - the exact command you start xclock with, including all parameters and
>   switches
> - versions of other important things I probably have forgotten
> 
> 
> +-----------------------------------------------------------------------+
> | Please run the attached `fastclock' binary, it is an `optimized'      |
> | version of xclock, which runs about 60 times faster than the original.|
> | As I have never seen droppings, I can't tell you how long you have to |
> | run the program. If you see artifacts, please submit the information  |
> | above to 740@bugs.debian.org                                          |
> +-----------------------------------------------------------------------+
> 
> Thank you for your help,
> Marcus
> 
> 
> -- 
> "Rhubarb is no Egyptian god."        Debian GNU/Linux        finger brinkmd@ 
> Marcus Brinkmann                   http://www.debian.org    master.debian.org
> Marcus.Brinkmann@ruhr-uni-bochum.de                        for public  PGP Key
> http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/       PGP Key ID 36E7CD09
> 

--
Alexander Schwartz (alexander.schwartz@gmx.net)
http://ourworld.compuserve.com/homepages/alex_schwartz

[XF86Config (text/plain, inline)]

# XF86Config auto-generated by XF86Setup
#
# Copyright (c) 1996 by The XFree86 Project, Inc.

#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# See 'man XF86Config' for info on the format of this file

Section "Files"
   RgbPath    "/usr/X11R6/lib/X11/rgb"
   FontPath   "/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi"
EndSection

Section "ServerFlags"
EndSection

Section "Keyboard"
   Protocol        "Standard"
   AutoRepeat      500 30
   LeftAlt         Meta
   RightAlt        Meta
   ScrollLock      Compose
   RightCtl        Control
   XkbKeycodes     "xfree86"
   XkbTypes        "default"
   XkbCompat       "default"
   XkbSymbols      "us(pc101)"
   XkbGeometry     "pc"
   XkbRules        "xfree86"
   XkbModel        "pc101"
   XkbLayout       "de"
EndSection

Section "Pointer"
   Protocol        "Microsoft"
   Device          "/dev/mouse"
   BaudRate        1200
   Emulate3Timeout 50
   Resolution      100
   Emulate3Buttons
EndSection

Section "Monitor"
   Identifier      "Primary Monitor"
   VendorName      "Unknown"
   ModelName       "Unknown"
   HorizSync       30-95
   VertRefresh     50-160
   Modeline  "1024x768"  107.00 1024 1060 1252 1360 768 771 781 806 -hsync -vsync
   Modeline  "800x600"    69.65 800 864 928 1088 600 604 610 640 -hsync -vsync
   Modeline  "640x480"    45.80 640 672 768 864 480 488 494 530 -hsync -vsync
   Modeline  "640x400"    31.50 640 672 736 832 400 401 404 445 -hsync +vsync
   Modeline  "512x384"    22.00 512 528 592 640 384 385 388 404 -hsync -vsync
   Modeline  "480x300"    29.95 480 504 584 624 300 319 322 333 doublescan
   Modeline  "400x300"    25.00 400 424 488 520 300 319 322 333 doublescan
   Modeline  "320x240"    15.75 320 336 384 400 240 244 246 262 doublescan
   Modeline  "320x200"    12.59 320 336 384 400 200 204 205 225 doublescan
EndSection

Section "Device"
   Identifier      "Primary Card"
   VendorName      "Unknown"
EndSection

Section "Screen"
   Driver          "Accel"
   Device          "Primary Card"
   Monitor         "Primary Monitor"
   DefaultColorDepth 32
   BlankTime       0
   SuspendTime     0
   OffTime         0
   SubSection "Display"
      Depth        8
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
   SubSection "Display"
      Depth        15
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
   SubSection "Display"
      Depth        16
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
   SubSection "Display"
      Depth        24
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
   SubSection "Display"
      Depth        32
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
EndSection

Section "Screen"
   Driver          "SVGA"
   Device          "Primary Card"
   Monitor         "Primary Monitor"
   DefaultColorDepth 8
   BlankTime       0
   SuspendTime     0
   OffTime         0
   SubSection "Display"
      Depth        8
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
   SubSection "Display"
      Depth        15
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
   SubSection "Display"
      Depth        16
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
   SubSection "Display"
      Depth        24
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
   SubSection "Display"
      Depth        32
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
EndSection

Section "Screen"
   Driver          "VGA16"
   Device          "Primary Card"
   Monitor         "Primary Monitor"
   BlankTime       0
   SuspendTime     0
   OffTime         0
   SubSection "Display"
      Depth        4
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
EndSection

Section "Screen"
   Driver          "VGA2"
   Device          "Primary Card"
   Monitor         "Primary Monitor"
   BlankTime       0
   SuspendTime     0
   OffTime         0
   SubSection "Display"
      Depth        1
      Modes        "1024x768" "800x600" "640x480" "640x400" "512x384" "480x300" "400x300" "320x240" "320x200"
   EndSubSection
EndSection

[.config (text/plain, inline)]

#
# Automatically generated by make menuconfig: don't edit
#

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
CONFIG_KERNELD=y

#
# General setup
#
# CONFIG_MATH_EMULATION is not set
CONFIG_NET=y
# CONFIG_MAX_16M is not set
CONFIG_PCI=y
# CONFIG_PCI_OPTIMIZE is not set
# CONFIG_MCA is not set
CONFIG_SYSVIPC=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_JAVA is not set
CONFIG_KERNEL_ELF=y
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M686 is not set
# CONFIG_BIGPHYS_AREA is not set

#
# Floppy, IDE, and other block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_IDE_PCMCIA is not set
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_TRITON=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_STRIPED=m
CONFIG_BLK_DEV_RAM=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_DEV_HD is not set

#
# Networking options
#
CONFIG_FIREWALL=y
CONFIG_NET_ALIAS=y
CONFIG_INET=y
CONFIG_IP_FORWARD=y
CONFIG_IP_MULTICAST=y
CONFIG_SYN_COOKIES=y
CONFIG_IP_FIREWALL=y
CONFIG_IP_FIREWALL_VERBOSE=y
CONFIG_IP_MASQUERADE=y
CONFIG_IP_MASQUERADE_IPAUTOFW=y
CONFIG_IP_MASQUERADE_ICMP=y
CONFIG_IP_TRANSPARENT_PROXY=y
CONFIG_IP_ALWAYS_DEFRAG=y
CONFIG_IP_ACCT=y
# CONFIG_IP_ROUTER is not set
# CONFIG_NET_IPIP is not set
# CONFIG_IP_MROUTE is not set
CONFIG_IP_ALIAS=m
# CONFIG_INET_PCTCP is not set
# CONFIG_INET_RARP is not set
# CONFIG_NO_PATH_MTU_DISCOVERY is not set
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y
CONFIG_IPX=m
CONFIG_ATALK=m
# CONFIG_AX25 is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETLINK is not set

#
# SCSI support
#
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
CONFIG_CHR_DEV_SG=y
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set

#
# SCSI low-level drivers
#
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
CONFIG_SCSI_AIC7XXX=y
# CONFIG_OVERRIDE_CMDS is not set
# CONFIG_AIC7XXX_PROC_STATS is not set
CONFIG_AIC7XXX_RESET_DELAY=5
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA_DMA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_NCR53C8XX is not set
CONFIG_SCSI_PPA=m
# CONFIG_SCSI_PPA_HAVE_PEDANTIC is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_GDTH is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_EQUALIZER is not set
# CONFIG_DLCI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
# CONFIG_SLIP is not set
# CONFIG_NET_RADIO is not set
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
CONFIG_EL3=m
# CONFIG_3C515 is not set
# CONFIG_VORTEX is not set
# CONFIG_NET_VENDOR_SMC is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_EEXPRESS_PRO100B is not set
# CONFIG_DE4X5 is not set
# CONFIG_DEC_ELCP is not set
# CONFIG_DGRS is not set
CONFIG_NE2K_PCI=m
# CONFIG_YELLOWFIN is not set
# CONFIG_RTL8139 is not set
# CONFIG_EPIC is not set
# CONFIG_TLAN is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_MCA is not set
# CONFIG_NET_EISA is not set
# CONFIG_NET_POCKET is not set
# CONFIG_TR is not set
# CONFIG_FDDI is not set
# CONFIG_ARCNET is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# CD-ROM drivers (not for SCSI or IDE/ATAPI drives)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Filesystems
#
CONFIG_QUOTA=y
CONFIG_MINIX_FS=y
CONFIG_EXT_FS=m
CONFIG_EXT2_FS=y
CONFIG_XIA_FS=m
CONFIG_NLS=m
CONFIG_ISO9660_FS=m
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_UMSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_KOI8_R=m
CONFIG_PROC_FS=y
CONFIG_NFS_FS=y
# CONFIG_ROOT_NFS is not set
CONFIG_SMB_FS=m
CONFIG_SMB_WIN95=y
# CONFIG_NCP_FS is not set
CONFIG_HPFS_FS=m
CONFIG_SYSV_FS=m
CONFIG_AUTOFS_FS=m
# CONFIG_AFFS_FS is not set
# CONFIG_UFS_FS is not set

#
# Character devices
#
CONFIG_SERIAL=y
# CONFIG_DIGI is not set
# CONFIG_CYCLADES is not set
# CONFIG_STALDRV is not set
# CONFIG_RISCOM8 is not set
CONFIG_PRINTER=m
# CONFIG_SPECIALIX is not set
# CONFIG_MOUSE is not set
# CONFIG_UMISC is not set
# CONFIG_QIC02_TAPE is not set
# CONFIG_FTAPE is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
# CONFIG_APM_CPU_IDLE is not set
CONFIG_APM_DISPLAY_BLANK=y
CONFIG_APM_POWER_OFF=y
# CONFIG_APM_IGNORE_MULTIPLE_SUSPEND is not set
# CONFIG_WATCHDOG is not set
CONFIG_RTC=y

#
# Sound
#
CONFIG_SOUND=y
# CONFIG_PAS is not set
CONFIG_SB=y
# CONFIG_ADLIB is not set
# CONFIG_GUS is not set
# CONFIG_MPU401 is not set
# CONFIG_UART6850 is not set
# CONFIG_PSS is not set
# CONFIG_GUS16 is not set
# CONFIG_GUSMAX is not set
# CONFIG_MSS is not set
# CONFIG_SSCAPE is not set
# CONFIG_TRIX is not set
# CONFIG_MAD16 is not set
# CONFIG_CS4232 is not set
# CONFIG_MAUI is not set
CONFIG_AUDIO=y
CONFIG_MIDI=y
CONFIG_YM3812=y
SBC_BASE=220
SBC_IRQ=5
SBC_DMA=1
SB_DMA2=5
SB_MPU_BASE=330
SB_MPU_IRQ=-1
DSP_BUFFSIZE=65536
CONFIG_LOWLEVEL_SOUND=y
CONFIG_ACI_MIXER=y

#
# Kernel hacking
#
# CONFIG_PROFILE is not set

[system.fvwm95rc (text/plain, inline)]

#
# Configuration file for fvwm95
# by Daniel Martin
#
# Much of this was inspired by/stolen from the fvwm2 configuration file.
# (by Lars Wirzenius)
# The easiest way to explain everything is to say "install fvwm2 and
# read /usr/doc/fvwm2/README.sysrc"
#

#
# Use pre.hook for things that need to be done before anything else.
# For example, a PixmapPath might be defined here.
#

Read /etc/X11/fvwm95/pre.hook
Read .fvwm95/pre.hook

#========================================================================#

#
# Fonts - one for window titles, another for icons, and another for the menus
#
WindowFont	-adobe-helvetica-bold-r-*-*-12-*-*-*-*-*-*-*
IconFont	fixed
MenuFont   	-adobe-helvetica-medium-r-*-*-*-120-*-*-*-*-*-*

#
# Set the default window colors. The syntax is:
#  DefaultColors winforecolor winbackcolor titleforecolor titlebackcolor
# where:
#  winbackcolor    is the background (border) color of all windows,
#                  including the menu windows 
#  winforecolor    is used for the menu text
#  titlebackcolor  is the background color used for title bars of 
#                  non selected windows
#  titleforecolor  is the color of the title text of non selected windows
#
DefaultColors   Black #c0c0c0 #c0c0c0 grey51

#
# Text and background color for the title bar of the active (selected) window
#
HilightColors   White #000080

#
# Text and background color for the title bar of sticky windows
#
StickyColors    grey51 #60c080

# You can also use the Style command to set the colors of individual
# title bars of some non-selected windows


#Style "*" ForeColor #c0c0c0
#Style "*" BackColor grey51

#========================================================================#

#
# Set up the major operating modes
#

Style "*" ClickToFocus
# Comment the above and uncomment one of the following if you prefer
# focus follow mouse.
#Style "*" MouseFocus
#Style "*" SloppyFocus

# If we use the FvwmTaskBar we don't need the icons :-)
# Style "..." Icon are also commented below.
Style "*" NoIcon
Style "*" MWMFunctions
Style "*" HintOverride
Style "*" MWMDecor
Style "*" DecorateTransient

OpaqueMoveSize 100
EdgeScroll 100 100
EdgeResistance 10000 0

#
# RandomPlacement prevents user interaction while placing windows:
#
Style "*" RandomPlacement

#
# NoPPosition instructs fvwm to ignore the PPosition field in window 
# geometry hints. Emacs annoyingly sets PPosition to (0,0)!
#
Style "*" NoPPosition

#========================================================================#

#
# Set the desk top size in units of physical screen size
#

DeskTopSize 3x2

#========================================================================#

#
# Module path and paths to the icons
# ModulePath is a colon-separated list, just like regular unix PATH
#
ModulePath /usr/X11R6/lib/X11/fvwm95/
PixmapPath /usr/X11R6/pixmaps:/usr/X11R6/include/X11/pixmaps/:/usr/X11R6/include/pixmaps/:/usr/local/lib/mini-icons/
IconPath   /usr/X11R6/include/X11/pixmaps:/usr/X11R6/include/X11/bitmaps:/usr/X11R6/include/pixmaps:/usr/X11R6/include/bitmaps/:/usr/local/lib/icons/

#========================================================================#

# Set the decoration styles and window options
# If compatible styles are set for a single window in multiple Style
# commands, then the styles are ORed together. If conflicting styles
# are set, the last one specified is used.

# These commands should command before any menus or functions are defined,
# and before the internal pager is started.

#
# Default border and handle widths
#
Style "*" BorderWidth 5, HandleWidth 5

Style "Fvwm*"        NoTitle, Sticky, WindowListSkip
Style "Fvwm Pager"   StaysOnTop, NoHandles
Style "FvwmBanner"   StaysOnTop
Style "FvwmButtons"  NoTitle, NoHandles, Sticky, WindowListSkip,BorderWidth 5
Style "*lock"        NoTitle, NoHandles, Sticky, WindowListSkip
Style "xbiff"        NoTitle,            Sticky, WindowListSkip

#
# Some mini-icons for the title bar
#
Style "*"         TitleIcon mini-x2.xpm
Style "*xterm*"   TitleIcon mini-term.xpm
Style "rxvt"      TitleIcon mini-term.xpm
Style "xcalc"     TitleIcon mini-calc.xpm
Style "xsession"  TitleIcon mini-bx2.xpm
Style "xv"        TitleIcon mini-xv.xpm
Style "Netscape"  TitleIcon mini-nscape.xpm
Style "xmag"      TitleIcon mini-zoom.xpm
Style "editor"    TitleIcon mini-edit.xpm
Style "tkps"      TitleIcon mini-run.xpm
Style "Ghostview" TitleIcon mini-gv.xpm
Style "Xcolorsel" TitleIcon mini-colors.xpm
Style "IDL*"      TitleIcon mini-zoom.xpm
Style "xeyes"     TitleIcon mini-eyes.xpm
Style "*fm*"      TitleIcon mini-filemgr.xpm
# xman resource names
Style "topBox"    TitleIcon mini-book1.xpm
Style "help"      TitleIcon mini-book2.xpm
Style "manualBrowser" TitleIcon mini-book2.xpm
# xpaint resource names
Style "xpaint"    TitleIcon mini-paint.xpm
Style "Canvas"    TitleIcon mini-paint.xpm
Style "fatbits"   TitleIcon mini-paint.xpm
Style "filebrowser" TitleIcon mini-ofolder.xpm

Style "FvwmFile"  TitleIcon mini-ofolder.xpm
Style "XDbx"      TitleIcon mini-bug2.xpm


#Style "rxvt"       Icon  term.xpm
#Style "xterm"      Icon xterm.xpm
#Style "color_xterm" Icon rterm.xpm
#Style "Appointment" Icon datebook.xpm
#Style "xcalc"      Icon Rcalc.xpm
#Style "xbiff"      Icon mail1.xpm
#Style "xmh"        Icon mail1.xpm, StartsOnDesk 2
#Style "xman"	   Icon xman.xpm
#Style "xvgr"	   Icon graphs.xpm
#Style "matlab"	   Icon math4.xpm
#Style "xmag"	   Icon mag_glass.xpm
#Style "xgraph"	   Icon graphs.xpm
#Style "xv"         Icon xview.xpm
#Style "FvwmButtons"  Icon toolbox.xpm
#Style "xconsole"   Icon koala.xpm
#Style "xsession"   Icon koala.xpm
#Style "editor"   Icon textedit.xpm
#Style "ghostview"  Icon gv.xpm

#========================================================================#

#
# Stuff to do at start-up
# For example, if you also have fvwm2 installed, you might add 
# + "I" Exec setup-background
# to your .fvwm95/init.hook
#
# The init.hook, init-restart.hook and restart.hook files should
# contain continuation lines, eg:
#       + "I" Exec xterm
#
#

AddToFunc "InitFunction"    "I" Exec xsetroot -solid cyan4 &
Read /etc/X11/fvwm95/init.hook
Read /etc/X11/fvwm95/init-restart.hook
Read .fvwm95/init.hook
Read .fvwm95/init-restart.hook


AddToFunc "RestartFunction" 
Read /etc/X11/fvwm95/restart.hook
Read /etc/X11/fvwm95/init-restart.hook
Read .fvwm95/restart.hook
Read .fvwm95/init-restart.hook

#========================================================================#

# Now define some handy complex functions

#
# This one moves and then raises the window if you drag the mouse,
# only raises the window if you click, or does a full maximize if 
# you double click
#
AddToFunc "Move-or-Raise" "M" Move
+                         "M" Raise
+                         "C" Raise
+                         "D" Maximize 100 100

#
# This one moves and then lowers the window if you drag the mouse,
# only lowers the window if you click, or does a RaiseLower if you double 
# click
#
AddToFunc "Move-or-Lower" "M" Move
+                         "M" Lower
+                         "C" Lower
+                         "D" RaiseLower

#
# This one moves or (de)iconifies:
#
AddToFunc "Move-or-Iconify" "M" Move
+                           "D" Iconify

#
# This one resizes and then raises the window if you drag the mouse,
# only raises the window if you click,  or does a RaiseLower if you double 
# click
#
AddToFunc "Resize-or-Raise" "M" Resize
+                           "M" Raise
+                           "C" Raise
+                           "D" RaiseLower


#
# The main menu.
#

#
# Read in system and user menu definitions.
#

# Read system and user menu prefixes
AddToMenu /Debian
+ "DebianMenu" Title
Read /etc/X11/fvwm95/main-menu-pre.hook
Read .fvwm95/main-menu-pre.hook

# Read the auto-generated menus
Read /etc/X11/fvwm95/menudefs.hook
Read .fvwm95/menudefs.hook

# Add in user additions
Read /etc/X11/fvwm95/main-menu.hook
Read .fvwm95/main-menu.hook

# Tack a quit entry on to the end
AddToMenu /Debian
+       ""                      Nop
+       "Exit Fvwm"             Popup Quit-Verify


#========================================================================#
#
# The Window-Ops menu is for manipulating windows.  It is invoked either
# from the main menu, or directly from the root window.
#

#
# This defines the most common window operations
#
AddToMenu "Window" "Window Ops" Title
+ "&Move"                     Function Move-or-Raise
+ "&Resize"                   Function Resize-or-Raise
+ "R&aise%mini-raise.xpm%"    Raise
+ "&Lower%mini-lower.xpm%"    Lower
+ "(De)Iconify"               Iconify
+ "(Un)Stick"                 Stick
+ "(Un)Maximize"              Maximize 100 100
+ ""                          Nop
+ "Kill"                      Destroy
+ "&Close"                    Delete
+ ""                          Nop
+ "Switch to..."              WindowList
+ "Refresh Screen%mini-ray.xpm%" Refresh

# This menu is invoked as a sub-menu - it allows you to quit,
# restart, or switch to another WM.

AddToMenu "Quit-Verify" "Really Quit Fvwm?" Title
+ "Restart%mini-turn.xpm%"		Restart fvwm95
+ "" 					Nop
+ "Yes, Really Quit%mini-exclam.xpm%"	Quit
+ "No, Don't Quit%mini-cross.xpm%" 	Nop


#
# A trimmed down version of "Window Ops", good for binding to decorations
#
AddToMenu "Window-Ops2" "&Restore"        Iconify -1
+                       "&Move"           Move-or-Raise
+                       "&Size"           Resize-or-Raise
+                       "Mi&nimize"       Iconify 1
+                       "Ma&ximize"       Maximize 100 100
+                       ""                Nop
+                       "&Kill"           Destroy
+                       "&Close	Alt+F4"   Delete

#========================================================================#

#
# One more complex function - couldn't be defined earlier because it used 
# pop-up menus
#
# This creates the "system" menu for the title-bar window-ops
# pop-up
#
AddToFunc "window_ops_func" "C" PopUp Window-Ops2
+              "M" PopUp Window-Ops2
+              "D" Delete  


#========================================================================#

#
# Mouse bindings
#

# First, for the mouse in the root window
# Button 1 gives the Utilities menu
# Button 2 gives the Window Ops menu
# Button 3 gives the WindowList (like TwmWindows)
# I use the AnyModifier (A) option for the modifier field, so you can hold down
# any shift-control-whatever combination you want!

#     Button	Context Modifi 	Function
Mouse 1		R   	A       Menu "/Debian" Nop
Mouse 2		R    	A       Menu "Window Ops" Nop
Mouse 3         R       A       WindowList
#Mouse 3	R    	A      	Module "winlist" FvwmWinList transient

# Now the title bar buttons
# Any button in the left title-bar button gives the window ops menu
# Any button in the first right title-bar button Iconifies the window
# Any button in the second title-bar button full-maximizes
# Any button in the third (rightmost) title-bar button closes
# Note the use of "Mouse 0" for AnyButton.

#     Button	Context Modif 	Function
Mouse 0		1    	A      	Function "window_ops_func"
Mouse 1         2       A       Delete
Mouse 0		4    	A     	Maximize 100 100
Mouse 0		6    	A     	Iconify

#
# Now the rest of the frame
# Here I invoke my complex functions for Move-or-lower, Move-or-raise,
# and Resize-or-Raise. 
#
# Button 1 in the corner pieces, with any modifiers, gives resize or raise
Mouse 1		F	A	Function "Resize-or-Raise"
# Button 1 in the title, sides, or icon, w/ any modifiers, gives move or raise
Mouse 1		TS	A	Function "Move-or-Raise"

# Button 1 in an icons gives move for a drag, de-iconify for a double-click,
# nothing for a single click
# Button 2 in an icon, w/ any modifiers, gives de-iconify
Mouse 1		I	A	Function "Move-or-Iconify"
Mouse 2		I	A	Iconify

# Button 2 in the corners, sides, or title-bar gives the window ops menu
Mouse 2		FST	A	Function "window_ops_func"

# Button 3 anywhere in the decoration (except the title-bar buttons)
# does a raise-lower
Mouse 3		TSIF	A	RaiseLower

# Button 3 in the window, with the Modifier-1 key (usually alt or diamond)
# gives Raise-Lower. Used to use control here, but that interferes with xterm
Mouse 3         W       M       RaiseLower

#========================================================================#

# Now some keyboard shortcuts.

# Arrow Keys
# press arrow + control anywhere, and scroll by 1 page
Key Left	A	C	Scroll -100 0
Key Right	A	C	Scroll +100 +0
Key Up		A	C	Scroll +0   -100
Key Down	A	C	Scroll +0   +100

# press arrow + meta key, and scroll by 1/10 of a page
Key Left	A	M	Scroll -10 +0
Key Right	A	M	Scroll +10 +0
Key Up		A	M	Scroll +0   -10
Key Down	A	M	Scroll +0   +10

# press shift arrow + control anywhere, and move the pointer by 1% of a page
Key Left	A	SC	CursorMove -1 0
Key Right	A	SC	CursorMove +1 +0
Key Up		A	SC	CursorMove +0   -1
Key Down	A	SC	CursorMove +0   +1

# press shift arrow + meta key, and move the pointer by 1/10 of a page
Key Left	A	SM	CursorMove -10 +0
Key Right	A	SM	CursorMove +10 +0
Key Up		A	SM	CursorMove +0   -10
Key Down	A	SM	CursorMove +0   +10

# Keyboard accelerators
Key F1		A	M	Popup "/Debian"
Key F2		A	M	Popup "Window Ops"
Key F3		A	M	Module "WindowList" FvwmWinList 
Key F4		A	M	Iconify
Key F5		A	M	Move
Key F6		A	M	Resize

#Page Up/Dapge Down keys are used to scroll by one desktop page
# in any context, press page up/down + control
# in root context, just pressing page up/down is OK
# 
# I prefer the non-wrapping scroll. These are for example purposes only
#Key Next	A       C       Scroll 100000 0
#Key Next	R       N       Scroll 100000 0  
#Key Prior	A       C       Scroll -100000 0
#Key Prior	R       N       Scroll -100000 0

Key Tab         A       M       Prev Focus
Key Tab         A       MS      Next Focus

Key Escape      A       C       WindowList

#========================================================================#

# Definitions used by the modules

#------------------ RunDialog (an FvwmForm incarnation)
*RunDialogFont *helvetica*m*r*n*14*
*RunDialogButtonFont *helvetica*m*o*n*14*
*RunDialogWarpPointer
*RunDialogFore       black
*RunDialogBack       gray70
*RunDialogItemBack   gray90
*RunDialogItemFore   black
*RunDialogLine       left
*RunDialogText       "Command: "
*RunDialogInput      cmd 30
*RunDialogLine       center
*RunDialogButton     quit "Run" ^M
*RunDialogCommand    Exec $(cmd)
*RunDialogButton     quit "Cancel" ^[
*RunDialogCommand    Nop

#------------------ Pager
*FvwmPagerBack grey60
*FvwmPagerFore black
*FvwmPagerFont -adobe-helvetica-bold-r-*-*-10-*-*-*-*-*-*-*
*FvwmPagerHilight #c0c0c0
*FvwmPagerGeometry -1-1
*FvwmPagerLabel 0 Desktop
*FvwmPagerSmallFont 5x8

#------------------ FvwmButtons (from 2.0.42)
*DebianFvwm95ButtonsFore Black
*DebianFvwm95ButtonsBack #c0c0c0
*DebianFvwm95ButtonsFont -adobe-helvetica-bold-r-*-*-10-*-*-*-*-*-*-*
# Geometry - really likes to pick its own size, but giving a position is OK
*DebianFvwm95ButtonsGeometry -5-34
# Layout: specify rows or columns, not both
*DebianFvwm95ButtonsRows 1

# Define the buttons to use.....

*DebianFvwm95Buttons(Title xclock, Icon clock.xpm, \
             Swallow(UseOld) "xclock" 'Exec /usr/bin/X11/xclock -bg \#c0c0c0 \
             -padding 0 -geometry -1500-1500 &')
*DebianFvwm95Buttons(10x1\
             Swallow(UseOld) "procmeter" 'Exec /usr/bin/X11/procmeter \
                     -bg grey70 -update 5 -geometry -1500-1500 -horizontal load cpu-user cpu-nice cpu-sys disk fpkt mem-used &')
#*DebianFvwm95Buttons(2x1, Title load, \
#             Swallow(UseOld) "xload" 'Exec /usr/bin/X11/xload \
#                     -nolabel -bg grey60 -update 5 -geometry -1500-1500 &')
#*DebianFvwm95Buttons(Title xterm, Icon rterm.xpm, \
#             Action 'Exec "XTerm" xterm \
#                     -ls -sb -fn 8x13 -title "Color xterm" &')
*DebianFvwm95Buttons(Title Files, Icon Xfm.xpm, \
             Action 'Exec "Files" files &') 
#*DebianFvwm95Buttons(Title Editor, Icon textedit.xpm, \
#             Action 'Exec "editor" editor &')
#*DebianFvwm95Buttons(Title xcalc, Icon rcalc.xpm, \
#             Action 'Exec "Calculator" xcalc &')
#*DebianFvwm95Buttons(Title xview, Icon xview.xpm, \
#             Action 'Exec "xv" xv &')
#*DebianFvwm95Buttons(Title gview, Icon gv.xpm, \
#             Action 'Exec "ghostview" ghostview &')
*DebianFvwm95Buttons(Title gview, Icon gv.xpm, \
             Action 'Exec "gv" gv &')
#*DebianFvwm95Buttons(Title netscape, Icon nscape.xpm, \
#             Action 'Exec "Netscape" netscape -geometry 920x622+90+5 &')
*DebianFvwm95Buttons(Title netscape, Icon nscape.xpm, \
             Action 'Exec "Netscape" netscape &')
*DebianFvwm95Buttons(Title kill, Icon rbomb.xpm, Action Destroy)
*DebianFvwm95Buttons(2x1, Swallow(UseOld) "Desktop" 'FvwmPager 0 0')

#------------------ Identify
*FvwmIdentBack #000080
*FvwmIdentFore Yellow
*FvwmIdentFont -adobe-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*

#------------------ FvwmWinList
*FvwmWinListBack #c0c0c0
*FvwmWinListFore Black
*FvwmWinListFont -adobe-helvetica-bold-r-*-*-10-*-*-*-*-*-*-*
*FvwmWinListAction Click1 Iconify -1,Focus
*FvwmWinListAction Click2 Iconify
*FvwmWinListAction Click3 Module "FvwmIdent" FvwmIdent
*FvwmWinListUseSkipList
*FvwmWinListGeometry +0-1
*FvwmWinListShowCurrentDesk
        
#------------------ FvwmTaskBar
Style "FvwmTaskBar" NoTitle,BorderWidth 4,HandleWidth 4,Sticky,StaysOnTop,WindowListSkip,CirculateSkip

*FvwmTaskBarGeometry +0-0
*FvwmTaskBarFore Black
*FvwmTaskBarBack #c0c0c0
*FvwmTaskBarTipsFore black
*FvwmTaskBarTipsBack bisque
*FvwmTaskBarFont -adobe-helvetica-medium-r-*-*-*-120-*-*-*-*-*-*
*FvwmTaskBarSelFont -adobe-helvetica-bold-r-*-*-*-120-*-*-*-*-*-*
*FvwmTaskBarAction Click1 Iconify -1,Raise,Focus
*FvwmTaskBarAction Click2 Iconify
*FvwmTaskBarAction Click3 Module "FvwmIdent" FvwmIdent
*FvwmTaskBarUseSkipList
*FvwmTaskBarAutoStick
*FvwmTaskBarStartName Start
*FvwmTaskBarStartMenu /Debian
*FvwmTaskBarStartIcon mini-exp.xpm
*FvwmTaskBarShowTips
#*FvwmTaskBarShowTransients
#*FvwmTaskBarClockFormat %I:%M%p
#*FvwmTaskBarHighlightFocus
#*FvwmTaskBarAutoHide
*FvwmTaskBarMailCommand Exec xterm -T Mail -ls -fn 8x13 -e pine -i

Read /etc/X11/fvwm95/post.hook
Read .fvwm95/post.hook

[xserver.out (text/plain, inline)]

XFree86 Version 3.3.2.3 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: July 15 1998
	If the server is older than 6-12 months, or if your card is newer
	than the above date, look for a newer version before reporting
	problems.  (see http://www.XFree86.Org/FAQ)
Operating System: Linux 2.0.35 i686 [ELF] 
Configured drivers:
  Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 0)
(using VT number 7)

XF86Config: /etc/X11/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) XKB: keycodes: "xfree86"
(**) XKB: types: "default"
(**) XKB: compat: "default"
(**) XKB: symbols: "us(pc101)"
(**) XKB: geometry: "pc"
(**) XKB: rules: "xfree86"
(**) XKB: model: "pc101"
(**) XKB: layout: "de"
(**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200
(**) Mouse: resolution: 100, buttons: 3
(**) Mouse: 3 button emulation (timeout: 50ms)
(**) Mach64: Graphics device ID: "Primary Card"
(**) Mach64: Monitor ID: "Primary Monitor"
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi"
(--) Mach64: PCI: Mach64 RageII+DVD rev 154, Aperture @ 0xe2000000, Registers @ 0xe0800000, Block I/O @ 0xb400
(--) Mach64: Card type: PCI
(--) Mach64: Memory type: 3
(--) Mach64: Clock type: Internal
(--) Mach64: Maximum allowed dot-clock: 200.000 MHz
(**) Mach64: Mode "1024x768": mode clock = 107.000
(**) Mach64: Mode "800x600": mode clock =  69.650
(**) Mach64: Mode "640x480": mode clock =  45.800
(**) Mach64: Mode "640x400": mode clock =  31.500
(**) Mach64: Mode "512x384": mode clock =  22.000
(**) Mach64: Mode "480x300": mode clock =  29.950
(**) Mach64: Mode "400x300": mode clock =  25.000
(**) Mach64: Mode "320x240": mode clock =  15.750
(**) Mach64: Mode "320x200": mode clock =  12.590
(--) Mach64: Virtual resolution: 1024x768
(--) Mach64: Video RAM: 4096k
(--) Mach64: Using hardware cursor
(--) Mach64: Using 16 MB aperture @ 0xe2000000
(--) Mach64: Using 4 KB register aperture @ 0xe0800000
(--) Mach64: Ramdac is Internal
(--) Mach64: Ramdac speed: 200 MHz
(--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 slots
(--) Mach64: Font cache: 0 fonts

Message #118 received at 740@bugs.debian.org (full text, mbox, reply):

From: Jens Ritter <jens@hilbert.weh.rwth-aachen.de>

To: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>

Cc: 740@bugs.debian.org, debian-user@lists.debian.org

Subject: Re: Let's hunt the oldest bug!

Date: 11 Jan 1999 19:16:20 +0100

Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:

> --k+w/mQv8wyuph6w0
> Content-Type: text/plain; charset=us-ascii
[...]
> +-----------------------------------------------------------------------+
> | Please run the attached `fastclock' binary, it is an `optimized'      |
> | version of xclock, which runs about 60 times faster than the original.|
> | As I have never seen droppings, I can't tell you how long you have to |
> | run the program. If you see artifacts, please submit the information  |
> | above to 740@bugs.debian.org                                          |
> +-----------------------------------------------------------------------+


I run fastclock for about 14 days non stop (on the xdm login screen)
and have never seen droppings.

HTH,

Jens

-- 
Jens.Ritter@weh.rwth-aachen.de       grimaldi@debian.org
KeyID: 2048/E451C639 1998/01/28
Print: 5F 3D 43 1E 24 1E CC 48  1E 05 93 3A A7 10 73 37

Message #123 received at 740@bugs.debian.org (full text, mbox, reply):

From: Shaleh <shaleh@livenet.net>

To: grimaldi@debian.org

Cc: 740@bugs.debian.org, Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>

Subject: Re: Let's hunt the oldest bug!

Date: Mon, 11 Jan 1999 13:26:41 -0500 (EST)

On 11-Jan-99 Jens Ritter wrote:
> Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:
> 
>> --k+w/mQv8wyuph6w0
>> Content-Type: text/plain; charset=us-ascii
> [...]
>> +-----------------------------------------------------------------------+
>> | Please run the attached `fastclock' binary, it is an `optimized'      |
>> | version of xclock, which runs about 60 times faster than the original.|
>> | As I have never seen droppings, I can't tell you how long you have to |
>> | run the program. If you see artifacts, please submit the information  |
>> | above to 740@bugs.debian.org                                          |
>> +-----------------------------------------------------------------------+
> 
> 
> I run fastclock for about 14 days non stop (on the xdm login screen)
> and have never seen droppings.
> 

Been running it here on a Diamond S3 card in both xserver-svga and xserver-s3,
no sign of problems either.  Machine is a p75.

Message #134 received at 740@bugs.debian.org (full text, mbox, reply):

From: Zygo Blaxell <zblaxell@linuxmaster.hungrycats.org>

To: 740@bugs.debian.org

Subject: Random thought...

Date: Mon, 26 Jul 1999 14:39:17 -0400 (EDT)

>This seems to be a really strange bug. Xclock calls XDrawLines() to draw the
>outlines of the hands and XFillPolygon() to fill in the centre, and to erase
>an old hand, it should always call the same functions with the same set of
>points but with a different GC. Apparently the erasing doesn't always happen
>for some reason. From the screen shots, it looks like they aren't just
>single-pixel droppings; sometimes big parts of the hands are dropped behind
>(this would imply that it probably isn't a floating point calculation
>problem).

Hmmm...given that the problem seems to be related to VT switching in some
way, I wonder if the above paragraph is really true.  When switching from a
VT to X, the same function is _not_ used--the graphics accelerator hardware
is drawing the polygon when X is on the current VT, and the XFree86 software
emulation of that hardware is drawing the polygon otherwise.  When switching
from VT to X, the "erase" polygon is being drawn by a different function
than the previous "draw" polygon.  If those functions generate different
results, there will be droppings.  

If this theory is correct, then you should get droppings if you draw some
polygons on an X pixmap, copy the pixmap to the X display, then erase some
of the polygons from the same locations in the pixmal on the X display.
Anyone care to test that?

Myself, I've seen the problem on all of the Mach64 cards (probably more
than a dozen by now) I've used since 1995 or so.  I don't remember if 
Mach32 cards have this problem or not.  The other X servers I've tried don't
seem to have this problem--assuming that they can successfully switch
between VT and X at all (my particular I128 card, for instance, can't).

-- 
Zygo Blaxell, Linux Engineer, Corel Corporation.  zygob@corel.ca (work) or
zblaxell@furryterror.org (play).  Opinions above are my own, not Corel's.

Message #141 received at 740-submitter@bugs.debian.org (full text, mbox, reply):

From: branden@indy.progenylinux.com (Branden Robinson)

To: 740-submitter@bugs.debian.org

Subject: Re: xclock leaves "droppings" in its window [UPSTREAM]

Date: Wed, 8 Nov 2000 17:25:46 -0500

Are you able to reproduce this problem with the XFree86 34.0 server?

-- 
Branden Robinson          | GPG signed/encrypted mail welcome
branden@progeny.com       | 1024D/32222732
Senior Software Developer | E31E 8D74 4BFA 77C9 6560
Progeny Linux Systems     | 0560 137B F214 3222 2732

Message #146 received at 740-done@bugs.debian.org (full text, mbox, reply):

From: branden@deadbeast.net (Branden Robinson)

To: 740-done@bugs.debian.org

Subject: closing ancient bug

Date: Mon, 24 Dec 2001 01:07:37 -0500

[Message part 1 (text/plain, inline)]

Submitter was asked for more info over a year ago.

Submitter did not reply.

Package against which this bug was reported is no longer maintained
upstream.

There have been no similar reports against XFree86 4.x.

Closing this bug.  Especially since to get feedback from Ian Jackson you
have to close his bugs.  Asking nicely doesn't work.

-- 
G. Branden Robinson                |
Debian GNU/Linux                   |           If existence exists,
branden@deadbeast.net              |           why create a creator?
http://www.deadbeast.net/~branden/ |

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.