-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 14.06.2010 16:19, schrieb Ekkard Gerlach:
Bodo, You sent the fax to yourself, same physical ISDN line?
No, I didn't.
As I wrote in the original bug report I checked this with a Siemens HiPath PBX
as remote station.
That means I sent a fax to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giuseppe Sacco schrieb:
From my tests, the defoma Fontmap was not easy to use by textfmt, so, in
later packages I suggested to move from textfmt to enscript.
Hello Guiseppe,
/usr/bin/faxmail is a binary program that does not call external
Package: hylafax-client
Version: 2:6.0.3-5.1
Severity: normal
On my system faxmail printed error messages because it could not find some
font metrics files. This includes a bogus error message I already reported
at HylaFAX' bugzilla http://bugs.hylafax.org/show_bug.cgi?id=925
The real cause of
Package: hinfo
Version: 1.02-3.1
Severity: important
When hinfo-update is called manually or by cron job, I get error messages:
Cannot specify -r, -p or -N if -O is given.
Usage: wget [OPTION]... [URL]...
/var/lib/hinfo/dnsbl.ins.pl syntax OK
Cannot specify -r, -p or -N if -O is given.
Usage:
Package: pmx
Version: 2.5.15-1
Severity: normal
When using option AT in a PMX or M-Tx source file, PMX generates a .tex
file that contains \input tuplet but there doesn't seem to be any package
that provides the file tuplet.tex. (I looked on my system and tried to find
a package using the
Package: capi4hylafax
Version: 1:01.03.00.99.svn.300-12
Severity: important
When I send a fax with more than one page, the receiver gets the first page
but for the following pages only a header line.
This was reported by a company using an (unknown) electronic fax system as
receiving station and
Package: giarpfanoa
Version: 0.1.2
Severity: minor
Tags: patch
When I run giarpfanoa on my system, I get these two error messages:
/usr/share/giarpfanoa/hp-search-mac.mod: line 2: [: argument expected
/usr/share/giarpfanoa/nbtscan.mod: line 3: [: argument expected
My system does not have the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Guiseppe,
I try to explain the problem as I understand it.
faxsetup is normally used to create setup.cache. If something is wrong
with HylaFAX after some changes to the system or after an upgrade of
HylaFAX, the experts in the mailing list
Package: hylafax-server
Version: 2:4.3.1-3
Followup-For: Bug #402961
Hello Giuseppe,
IMHO a manual modification of setup.cache is only a workaround.
I think this is an upstream bug.
Running faxsetup is the recommended way to fix HylaFAX' configuration.
It is bad if faxsetup does not work
Bodo Meissner schrieb:
I think this is an upstream bug.
Sorry Giuseppe,
I think I was wrong.
My setup.cache had
AWK='/usr/bin/gawk'
in it. That's why I thought it might have been written there by faxsetup.
I looked into the faxsetup script and it seems to always write the
default value
Am 09.11.2006 05:28:18 schrieb(en) Junichi Uekawa:
Basically, I don't like the whole idea of having to handle
soap_use_proxy even in non-CGI environments. It's just so silly.
Hello Junichi,
after some searching I found information about the security risk which
is present in CGI programs.
Package: libruby1.8
Followup-For: Bug #396304
I think this bug is still related to apt-listbugs.
The soap_use_proxy variable is an interface of a library used internally.
apt-listbugs does not _have_to_ expose this interface to the user.
apt-listbugs even sets or deletes this variable in some
Package: squid
Version: 2.6.2-1
Followup-For: Bug #377697
I need squid with support for 2.4 kernel because the 2.6 kernels (for
686-smp) do not support AVM B1 ISDN cards (and similar active cards)
Bodo
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy:
Package: hylafax-server
Version: 2:4.3.0-5
Severity: minor
Tags: l10n
After installing the current unstable package I found that the notification
mail in German language was not displayed properly. (Non-ASCII characters
were missing in my case.)
The cause is a wrong charset declaration in the
Package: dosbox
Version: 0.63-2.1
Severity: wishlist
Please, build a Debian package of the current upstrem version.
The new version 0.65 is able to run programs created with Borland C or
Turbo Pascal which exit with a BGI error message in version 0.63.
Bodo
--
To UNSUBSCRIBE, email to [EMAIL
Package: gnome-terminal
Version: 2.12.0-2
Severity: normal
I found this problem in combination with seyon.
Seyon tries to create a terminal emulation window with this call:
14811 execve(/usr/bin/X11/seyon-emu, [seyon-emu, -name, Seyon, -T,
Seyon Terminal Emulator, -n, Terminal, -e, seyon,
Package: xlibs
Version: 6.8.2.dfsg.1-5
Severity: important
After upgrading to xserver-xorg I noticed that the key AltGr+Q which
should produce @ on a German keyboard did not work. Other key combinations
with AltGr like brackets and backslash did work.
Using search engines I found some hints
Package: tiger
Version: 1:3.2.1-26
Severity: wishlist
Tiger calls chkrootkit -q in /usr/lib/tiger/scripts/check_rootkit.
n my case this is very slow because it scans NFS directories.
I would like to have a configuration variable in /etc/tiger/tigerrc
which can be set to add option -n to the
Package: uclibc-toolchain
Version: 0.9.26-cvs20040816-5.1
Severity: important
/usr/bin/i386-uclibc-linux-gcc uses a hard coded directory
/usr/lib/gcc-lib/i486-linux/3.3.4 which requires a specific GCC version
but does not depend on a specific version
Currently I have gcc 3.3.5 and get error
Hello Matthias,
I don't have a patch, because I don't know enough about backage
building and the available make variables. But I think I found where a
change is needed.
I tried to build capi4hylafax from source package on my fax server
(dual Pentium pro) using apt-get source, apt-get
Hello Matthias,
in a German mailing list someone assumend that capi4hylafax might
report wrong capabilities which allows Hylafax to select an unsupported
TIFF file format.
On my system Hylafax reports
MODEM faxCAPI: READY, capabilities P3ffd:ff
I manually decoded the string and found that
Package: capi4hylafax
Version: 1:01.02.03-7
Followup-For: Bug #291559
The same problem occurs with version 1:01.02.03-9.
For now I'll stick with 1:01.02.03-7 and use my wrapper script
as workaround for bug #293808.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy:
Package: capi4hylafax
Version: 1:01.02.03-7
Followup-For: Bug #293808
Because bug #291559 is still present, I cannot check if the fix
for 293808 works.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Package: capi4hylafax
Version: 1:01.02.03-7
Followup-For: Bug #293808
I think I found the problem. This is my analysis:
Starting with Hylafax version 4.2.0, it writes a line returned:0 into
the queue file before starting SendFaxCmd. Versions 4.1.7 and 4.1.8 did
not do this.
c2faxsend doesn't
Package: capi4hylafax
Version: 1:01.02.03-7
Severity: important
I do not send faxes very often, so I don't know since when I have this
problem.
Hylafax repeatedly sends the fax and always gets SEND INCOMPLETE. When
it has reached the limit it tells that it could not send the fax.
The receiving
Package: capi4hylafax
Version: 1:01.02.03-7
Followup-For: Bug #291559
Segfault on receiving a fax on my system, too. (Sending not checked.)
Everything works after downgrading to 1:01.02.03-7.
c2faxrecv always creates a fax00*.tif containing 8 bytes.
# od -tx1 fax5.tif
000 49 49 2a 00 00
Am 2005.01.12 21:18 schrieb(en) Debian Bug Tracking System:
I think we may close this report since the new versions, starting at
4.2.0-16 were defining all these files config files.
Hello Giuseppe,
I agree that the problem is solved. Sure you can close the bug report.
(I did not know it was not
27 matches
Mail list logo
