Package: debauch
Version: 0.5-1
Hi,
When I run debauch with the new optimized libc6 package (libc6-i586) it
segfaults like so:
/usr/bin/debauch: line 36: 15259 Segmentation fault
DebauchWarnReferenced=$fullwarn DebauchWarnUnreferenced=$fullwarn
LD_PRELOAD=/usr/lib/libdebauch.so $OBJ $* 2>
Processing commands for [EMAIL PROTECTED]:
> tags 71280 + unreproducible
Bug#71280: djtools: djtools: Default setup (w/magicfilter) looses lines
Tags added: unreproducible
>
End of message, stopping processing here.
Please contact me if you need assistance.
Darren Benham
(administrator, Debian
* k e c h i e <[EMAIL PROTECTED]> [19990911 22:24]:
> lockvc could not unlock my vc even if I enter the root passwd.
> That's all
I just uploaded a new version of lockvc to woody. Can you please
try it out and tell me if you still see this problem?
--
Martin Michlmayr
[EMAIL PROTECTED]
Your message dated Sat, 09 Dec 2000 14:54:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#74240: fixed in lockvc 3.9-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 your r
Your message dated Sat, 09 Dec 2000 14:52:43 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#70246: fixed in dfm 0.99.7-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 your r
Your message dated Sat, 09 Dec 2000 14:52:42 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#67938: fixed in dfm 0.99.7-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 your r
Your message dated Sat, 09 Dec 2000 14:54:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#50811: fixed in lockvc 3.9-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 your r
Your message dated Sat, 09 Dec 2000 14:54:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#50721: fixed in lockvc 3.9-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 your r
Your message dated Sat, 09 Dec 2000 14:54:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#50474: fixed in lockvc 3.9-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 your r
Your message dated Sat, 09 Dec 2000 14:54:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#46964: fixed in lockvc 3.9-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 your r
Installing:
queue_1.20.1-pre4-8.dsc
to dists/woody/main/source/admin/queue_1.20.1-pre4-8.dsc
replacing queue_1.20.1-pre4-6.dsc
queue_1.20.1-pre4-8_i386.deb
to dists/woody/main/binary-i386/admin/queue_1.20.1-pre4-8.deb
replacing queue_1.20.1-pre4-6.deb
queue_1.20.1-pre4-8.tar.gz
to dists/
We believe that the bug you reported is fixed in the latest version of
lockvc, which has been installed in the Debian FTP archive:
lockvc_3.9-1.dsc
to dists/woody/main/source/utils/lockvc_3.9-1.dsc
replacing lockvc_3.4-3.dsc
lockvc_3.9-1_i386.deb
to dists/woody/main/binary-i386/utils/lockvc_3
We believe that the bug you reported is fixed in the latest version of
lockvc, which has been installed in the Debian FTP archive:
lockvc_3.9-1.dsc
to dists/woody/main/source/utils/lockvc_3.9-1.dsc
replacing lockvc_3.4-3.dsc
lockvc_3.9-1_i386.deb
to dists/woody/main/binary-i386/utils/lockvc_3
We believe that the bug you reported is fixed in the latest version of
lockvc, which has been installed in the Debian FTP archive:
lockvc_3.9-1.dsc
to dists/woody/main/source/utils/lockvc_3.9-1.dsc
replacing lockvc_3.4-3.dsc
lockvc_3.9-1_i386.deb
to dists/woody/main/binary-i386/utils/lockvc_3
We believe that the bug you reported is fixed in the latest version of
lockvc, which has been installed in the Debian FTP archive:
lockvc_3.9-1.dsc
to dists/woody/main/source/utils/lockvc_3.9-1.dsc
replacing lockvc_3.4-3.dsc
lockvc_3.9-1_i386.deb
to dists/woody/main/binary-i386/utils/lockvc_3
We believe that the bug you reported is fixed in the latest version of
lockvc, which has been installed in the Debian FTP archive:
lockvc_3.9-1.dsc
to dists/woody/main/source/utils/lockvc_3.9-1.dsc
replacing lockvc_3.4-3.dsc
lockvc_3.9-1_i386.deb
to dists/woody/main/binary-i386/utils/lockvc_3
We believe that the bug you reported is fixed in the latest version of
lockvc, which has been installed in the Debian FTP archive:
lockvc_3.9-1.dsc
to dists/woody/main/source/utils/lockvc_3.9-1.dsc
replacing lockvc_3.4-3.dsc
lockvc_3.9-1_i386.deb
to dists/woody/main/binary-i386/utils/lockvc_3
Installing:
lockvc_3.9-1.dsc
to dists/woody/main/source/utils/lockvc_3.9-1.dsc
replacing lockvc_3.4-3.dsc
lockvc_3.9-1_i386.deb
to dists/woody/main/binary-i386/utils/lockvc_3.9-1.deb
replacing lockvc_3.4-3.deb
lockvc_3.9.orig.tar.gz
to dists/woody/main/source/utils/lockvc_3.9.orig.tar.gz
We believe that the bug you reported is fixed in the latest version of
dfm, which has been installed in the Debian FTP archive:
dfm_0.99.7-1.dsc
to dists/woody/main/source/x11/dfm_0.99.7-1.dsc
replacing dfm_0.99.3-1.1.dsc
dfm_0.99.7-1_i386.deb
to dists/woody/main/binary-i386/x11/dfm_0.99.7-1.
We believe that the bug you reported is fixed in the latest version of
dfm, which has been installed in the Debian FTP archive:
dfm_0.99.7-1.dsc
to dists/woody/main/source/x11/dfm_0.99.7-1.dsc
replacing dfm_0.99.3-1.1.dsc
dfm_0.99.7-1_i386.deb
to dists/woody/main/binary-i386/x11/dfm_0.99.7-1.
Installing:
dfm_0.99.7-1.dsc
to dists/woody/main/source/x11/dfm_0.99.7-1.dsc
replacing dfm_0.99.3-1.1.dsc
dfm_0.99.7-1_i386.deb
to dists/woody/main/binary-i386/x11/dfm_0.99.7-1.deb
replacing dfm_0.99.3-1.1.deb
dfm_0.99.7.orig.tar.gz
to dists/woody/main/source/x11/dfm_0.99.7.orig.tar.gz
Package: chimera
Version: 1.70p1-1
In order to display jpegs in web pages, chimera needs djpeg, which comes
with libjpeg-progs. chimera doesn't even suggest libjpeg-progs at the
moment, so you don't get much warning of this. I'm new to Debian, so I don't
know if this qualifies for a "needs" relati
On Sat, Dec 09, 2000 at 10:13:53AM +0100, Christian Kurz wrote:
> On 00-12-09 Gordon Sadler wrote:
> > Pardon my ignorance, but the libpam-pwdb that this bug refers to not
> > being available seems to be in an odd position. It IS available,
> > however only on auric, testing. I track quite a few mi
On 00-12-09 Martin Michlmayr wrote:
> * Matthew Vernon <[EMAIL PROTECTED]> [20001209 00:15]:
> > tbm's package seems to be on ftp-master, so I'll wait and see what
> > happens (if there's a conflict use his instead of mine, since I just
> > hacked it to
On 00-12-09 Gordon Sadler wrote:
> Pardon my ignorance, but the libpam-pwdb that this bug refers to not
> being available seems to be in an odd position. It IS available,
> however only on auric, testing. I track quite a few mirrors, to
Well, maybe the maintainer of libpam-pwdb can comment on thi
[There's no need to Cc me, as I'm also on debian-qa, as you could assume
from my signature. ;)]
On 00-12-09 Matthew Vernon wrote:
> > Wichert just orphaned lockvc in IRC when I talked with him about the
> > release-critical-bug in it. I then tried to recompile lockvc here on
> > woody and make
Pardon my ignorance, but the libpam-pwdb that this bug refers to not
being available seems to be in an odd position. It IS available,
however only on auric, testing. I track quite a few mirrors, to
include testing, experimental apt, and experimental X4 but only
semi-official debs, no Helix or othe
27 matches
Mail list logo
