Re: [wm-user] WindowMaker 0.70.0-1
Okay, I'll try this, given time, over the next week
and report back. Question: how do I see what options
my windowmaker ( installed from a deb ) was built
with?
--- Dan Pascu <dan@services.iiruc.ro> wrote:
>
> I use debian unstable (up to date 18 Oct) and never
> encountered this
> behavior. You will have to narrow down the set of
> conditions that
> triggers this.
> You should recompile wmaker from source without any
> ./configure options
> and without any modification to wconfig.h
> Install it and create a new test user for which run
> wmaker.inst.
> Then try to see if the problem appears for that
> user. If not start
> adding all options you use 1 by 1 until the problem
> appears. If still
> don't start adding all the changes to the
> WindowMaker/dock/clip/WMWindowAttributes that you
> use for the user
> having the problem.
> Report back when you can narrow the problem down.
>
> On 19 Oct, Charles Baker wrote:
> > I had this same problem on testing/unstable as
> well,
> > but didn't associate it with the selection of
> > omnipresent on a window. However, I just tried it,
>
> > and sure enough that does send my cpu to full
> > utilization and unchecking drops it back down to
> > normal.
> >
> > --- Dan Pascu <dan@services.iiruc.ro> wrote:
> >>
> >> We got another report about this from another
> user,
> >> but couldn't
> >> reproduce this.
> >> Also I don't recall anything changed in the
> >> dock/clip code lately.
> >> Maybe it was there before, but you just happened
> to
> >> trigger the
> >> necessary conditions we haven't found yet.
> >> Also we don't use the debian packages, but we
> >> compile from source.
> >> See if it makes a difference and in this case
> there
> >> may be some patch
> >> the debian maintainer applied.
>
> --
> Dan
>
=====
-
rascharles@yahoo.com
Hacking is a "Good Thing!"
See http://www.tuxedo.org/~esr/faqs/hacker-howto.html
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
Reply to: