Manoj Srivastava <sriva...@acm.org> writes:

> On Wed, Apr 29 2009, Dan Espen wrote:
>
>> Manoj Srivastava <sriva...@acm.org> writes:
>>
>>> Hi,
>>>
>>>         I can send them here, of course,  if that ias acceptable. For
>>>  the record, these are the currently open bug reports for fvwm in the
>>>  Debian BTS.
>>>
>>>    http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=fvwm
>>
>> All these bugs seem to be Fvwm 1.
>
>         No. If you look at them, really, there are version numbers in
>  there. Most of them are 2.5.2X

The "odd" numbering threw me off.  For example:

Found in version fvwm/1:2.5.26-1

We would call that:

fvwm2/2.5.26

I can guess what the -1 at the end is but the 1 at the beginning
is confusing.

I don't have time to look at each of these.
Maybe if you submit them over a period of time.

I looked at:

FVWM: Very slow when moving audacious window by dragging it

I installed audacious and at first I didn't see anything odd.
Grab the Fvwm title bar and it moves just fine.
Click the Fvwm window operations menu, select move and then
click on the window and move it around like crazy.

Where it goes wrong is when you click on the applications
"phony" titlebar.  Then there is a serious lag before it starts
moving.

Going into preferences and selecting "show window manager decoration"
disabled movement from the "phony" titlebar completely.

I tested version 1.4.5.

XMMS has the same "phony" titlebar and it works fine.

I'm not sure if anyone here will be inclined or motivated
to fix this.


I looked at this one too:

fvwm: FVWM crashes when started in tightvncserver

Shouldn't this be closed due to this comment:

while debugging another issue with FVWM in a tightvncserver instance, I came
accross a SIGSEGV of FVWM when starting. It happens to the 2.5.25 debian
package, but not the the latest CVS HEAD.


That's all I have time for right now.  Sorry.

Reply via email to