Your message dated Sat, 11 Feb 2006 08:02:17 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#335899: fixed in lmodern 0.99.3-1
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 y
Your message dated Sat, 11 Feb 2006 08:02:17 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348906: fixed in lmodern 0.99.3-1
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 y
Your message dated Sat, 11 Feb 2006 15:17:19 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#268664: fixed in dosemu 1.2.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 you
Your message dated Sat, 11 Feb 2006 15:17:19 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#307021: fixed in dosemu 1.2.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 you
Your message dated Sat, 11 Feb 2006 15:17:18 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#249242: fixed in dosemu 1.2.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 you
Your message dated Sat, 11 Feb 2006 15:17:19 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332478: fixed in dosemu 1.2.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 you
Your message dated Sat, 11 Feb 2006 15:17:19 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#351016: fixed in dosemu 1.2.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 you
Your message dated Sat, 11 Feb 2006 16:47:13 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#302661: fixed in xdialog 2.1.2-1
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 yo
Your message dated Sat, 11 Feb 2006 16:47:13 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#306532: fixed in xdialog 2.1.2-1
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 yo
Your message dated Sat, 11 Feb 2006 16:47:13 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329717: fixed in xdialog 2.1.2-1
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 yo
Your message dated Sat, 11 Feb 2006 16:47:13 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332275: fixed in xdialog 2.1.2-1
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 yo
Your message dated Sat, 11 Feb 2006 16:47:13 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#342815: fixed in xdialog 2.1.2-1
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 yo
Hi,
thanks for fixing this, but did somebody investigate why kernel 2.4
dealt so badly with this segfault, and whether 3.1r2's 2.4 kernels have
this fixed? That issue is largely more worrying to me than the previous
xdialog's SEGV on 2.6 :/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
13 matches
Mail list logo