Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 3 Nov 1996 02:11:10 -0600 (CST)
From:      Dan Walters <hannibal@cyberstation.net>
To:        current@freebsd.org
Subject:   Re: Anyone using afterstep?
Message-ID:  <Pine.BSI.3.95.961103020647.6286A-100000@citrine.cyberstation.net>
In-Reply-To: <Pine.BSI.3.95.961102205501.24995B-100000@citrine.cyberstation.net>

next in thread | previous in thread | raw e-mail | index | archive | help
OK, I've been playing around, and it happens whenever I go wild on the
mouse buttons.  :)  It doens't happen after I kill moused, though -
something here I should know about?  It's a mouseman, about 2 months old,
moused runs like:  moused -c -p /dev/mouse -t mouseman

Also, power went out here about an hour ago, so I got to find a new quirk.
:)  In /etc/rc, there's already a "rm -f /dev/log", but with the devfs
changes, that's moved to /var/run/log and the /dev is only a symlink.
After the crash syslogd paused for a few seconds with an error because
taht already existed, so should prob. change it to /var/run.

======================================================================
Dan Walters
hannibal@cyberstation.net
======================================================================

On Sat, 2 Nov 1996, Dan Walters wrote:

> I'm using afterstep 1.0pre1, from the ports collection - probably about
> once or twice a day it tends to just lock up.  All other apps still run
> find, but of course I can't switch windows, the window manager keys don't
> work, mouse pointer is stuck in some non-client area of the windows
> (like the title bar,) etc. (In other words, it seems to be the WM.)  I've
> asked on the afterstep list, and none of them seem to be having problems,
> so I'm assuming it's something to do with FreeBSD (I'm sure they are all
> in Linux.)  I'm running 2.2-CURRENT, last make world was about a week ago,
> XFree86 3.2 (it happened on 3.1.2G too.)  I compiled with debugging and
> did a kill -11 to get a coredump just a second ago, but it didn't have a
> call stack so it didn't help me much.  I don't really know how to go about
> debugging a WM.  :)  Is this happening to anyone else?  Any ideas?
> 
> ======================================================================
> Dan Walters
> hannibal@cyberstation.net
> ======================================================================
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.961103020647.6286A-100000>