FVWM Bug Tracking notification

new message incoming/1030

Message summary for PR#1030
        From: [EMAIL PROTECTED]
        Subject: FvwmPager looses tracks of window goemetry
        Date: Tue, 13 May 2003 03:42:04 -0500
        0 replies       0 followups

====> ORIGINAL MESSAGE FOLLOWS <====

>From [EMAIL PROTECTED] Tue May 13 03:42:04 2003
Received: from lserv00.math.uh.edu ([129.7.128.99])
        by util2.math.uh.edu with esmtp (Exim 4.10)
        id 19FVMK-0007A5-00
        for [EMAIL PROTECTED]; Tue, 13 May 2003 03:42:04 -0500
Received: from localhost (lserv00.math.uh.edu [127.0.0.1])
        by lserv00.math.uh.edu (8.11.6/8.11.1) with ESMTP id h4D8g3m14823
        for <[EMAIL PROTECTED]>; Tue, 13 May 2003 03:42:04 -0500
Date: Tue, 13 May 2003 03:42:04 -0500
Message-Id: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: FvwmPager looses tracks of window goemetry

Full_Name: Roberto Ugoccioni
Version: 2.4.15
CVS_Date: 
OS: Linux RedHat 7.3 and SuSE 8.1
X_Server: XFree 4.2.0
Submission from: (NULL) (193.205.65.5)


I have FvwmPager swallowed by FvwmButtons. It happens occasionally,
unfortunately in conditions I cannot reproduce consistently,
that the pager suddenly shows the FvwmButtons window not as it is
(stretched across the top of the screen), but shrunk to a 
small rectangle in the top left corner of the screen. FvwmIdent
shows the correct geometry of the FvwmButtons window.
If I run another instance of FvwmPager, all is correct.
This behaviour only started to appear once I moved to 2.4.15;
I was using 2.4.5 before and never happened.

The same thing happens when FvwmPager is swallowed not by FvwmButtons,
but by another toolbar application I have written using tcl/tk with
TkXext extensions. In this case though the bug appears as soon as I
do something involving the window manager, all the time.




--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to