Your message dated Wed, 24 Mar 1999 01:53:25 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#34969: fvwm2: fvwm2: /etc/X11/fvwm2/menudefs.hook lists
modules in the wrong directory
has caused the attached bug report to be marked as done.
This means that you claim that
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Wed, 24 Mar 1999 01:33:11 + (GMT)
with message-id <[EMAIL PROTECTED]>
and subject line Bugs fixed etc. in FVWM 2.2
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
The following bugs should have been fixed or similar in the new fvwm
package, which has just been installed. (It is version 2.2-1.) Also
listed are a couple of bugs/wishlist items which appear unlikely to be
fixed for the time being.
Please let me know if there are still problems with these bugs
[EMAIL PROTECTED] writes:
> On 22 Mar, [EMAIL PROTECTED] wrote:
> > This is the second report of this. I do not see it on either hamm,
> > slink, or potato systems. Could you please try and recompile it,
> > maybe it is a glibc2.1 issue.
>
> Tried that. Same outcome. anacron -s hangs. Same sit
Package: fvwm2
Version: 2.1.10-2
Space: /etc/X11/fvwm2# grep Ident *
menudefs.hook:+ "FvwmId&ent" /usr/lib/X11/fvwm2/FvwmIdent
NoSpace:/etc/X11/fvwm2# locate FvwmIdent
/usr/X11R6/lib/fvwm2/fvwm/2.1.10/FvwmIdent
/usr/X11R6/man/man1/FvwmIdent.1.gz
So the modules aren't found.
-- System Informatio
27 matches
Mail list logo
