FVWM Bug Tracking notification
new message incoming/850
Message summary for PR#850
From: [EMAIL PROTECTED]
Subject: deiconify crashes with FvwmIconMan transient and FvwmWinList
transient
Date: Wed, 06 Feb 2002 10:43:11 -0600
0 replies 0 followups
====> ORIGINAL MESSAGE FOLLOWS <====
>From [EMAIL PROTECTED] Wed Feb 06 10:43:12 2002
Received: from karazm.math.uh.edu ([129.7.128.1])
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 16YVA8-0001Id-00
for [EMAIL PROTECTED]; Wed, 06 Feb 2002 10:43:12 -0600
Received: from malifon.math.uh.edu (IDENT:[EMAIL PROTECTED] [129.7.128.13])
by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id KAA22352
for <[EMAIL PROTECTED]>; Wed, 6 Feb 2002 10:43:12 -0600 (CST)
From: [EMAIL PROTECTED]
Received: from localhost ([127.0.0.1] ident=65534)
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 16YVA7-0001IZ-00
for [EMAIL PROTECTED]; Wed, 06 Feb 2002 10:43:11 -0600
To: [EMAIL PROTECTED]
Subject: deiconify crashes with FvwmIconMan transient and FvwmWinList transient
Message-Id: <[EMAIL PROTECTED]>
Date: Wed, 06 Feb 2002 10:43:11 -0600
Full_Name: Markus Schwarzenberg
Version: 2.4.5
CVS_Date:
OS: SunOS 5.7
X_Server:
Submission from: (NULL) (153.96.96.2)
Both FvwmWinList transient and FvwmIconMan transient
make fvwm segfaulting when trying to de-iconify an
iconified window which is shown in their window list:
The (complete!) .fvwm2rc to reproduce this is simple:
Mouse 1 1 N Close
Mouse 1 2 N Iconify true
Mouse 1 R A FvwmWinList Transient
Start fvwm2. Open some windows (xterm, for example) and
iconify a couple of them. Now, when Mouse 1 Btn is hit on the root
window, the window list pops up. Now click an entry of this list
for an iconified window: fvwm2 dies with a segfault, emmitting
the following message (generated in module_interface.c):
[FVWM][PositiveWrite]: <<ERROR>> Failed to read descriptor from
'FvwmWinList Tra
nsient':
- data available=Y
- terminate signal=N
[FVWM][PositiveWrite]: <<ERROR>> Failed to read descriptor from '
I'm not quite shure (but I think so) wether the first of these 1.5
error messages comes from a first (of the same session) try where
fvwm2 still didn't crash.
This happens with FvwmIconMan and FvwmWinList, so I suppose it's
not (only) a problem of these modules but an fvwm2 internal problem.
Markus Schwarzenberg
--
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]
