Bug#301994:
I wrote: > This looks similar to the empty page problem #295875. You wrote: Nope, I don't have a header line, actually I don't even have a page at all at the receiving end, it just times out waiting for data when c2faxsend is already down and hylafax thinks the fax has been successfully sent. Hello Remi, I'm not sure about this. In a mailing list I read that capi4hylafax transmits the header line when sending a TIFF file produced by ghostscript using device tiffg4 and nothing at all with a TIFF file produced using tiffg32d. (or vice versa) I tested different versions of c2faxsend and c2faxrecv on my system. With the broken version I received a notification mail that the fax was successfully sent but the receiver didn't get the document. The fixed version successfully transferred the document. So I think the fix for the segfault problem and the empty page problem might cure your problem as well. Bodo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301994: capi4hylafax: latest version looses faxes without warning
Hello Remi, thank you very much for this detailed information. Am 2005.03.30 11:29 schrieb(en) Rémi Letot: Here is the notification mail I receive : [...] Subject: facsimile job 10 to 081412841 completed [...] The sent queue is empty after it, and the done queue contains the fax. That means Hylafax definitely thinks the fax was successfully transferred. [...] Mar 30 11:07:39.26: [ 8552]: Page 1 was sended. - Last Page! Mar 30 11:07:39.26: [ 8552]: Fax file completely transfered to CAPI. Mar 30 11:07:39.41: [ 8552]: Connection dropped with Reason 0x3400 (No additiona Mar 30 11:07:39.42: [ 8552]: SESSION END This looks similar to the empty page problem #295875. Now I also tried to send a fax *to* the hylafax installation, and c2faxrecv died. This looks like the segfault problem #291559. Maybe your problem is a combination of other problems already reported. but I'll try your solution to #291559 in the near future and report if all goes well. The solution is not ready yet, at least no binary package to install. I still have a few questions: How did you submit the fax job? On a UNIX system with the sendfax command? On a Windows system using WHFC or another front end program? What type (Postscript/TIFF/Word document etc.) was the original file? Bodo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301994: capi4hylafax: latest version looses faxes without warning
Hello Remi, I really need some more information about this problem. The fact that you downgraded does not help me finding the bug. Can you remember some details? What do you mean with "hylafax behaves like they are sent ok"? Did you get a notification e-mail that the fax was successfully sent? Did the job appear in the done queue? The first thing to find out: Is the problem you reported different from #291559 "Capi4hylafax segfaults during send and receive"? Bodo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301994: capi4hylafax: latest version looses faxes without warning
Hello Remi, since the current maintainer indends to orphan the package, I'm trying to find some bugs and to supply patches. On my system versions 01.02.03-8 and 01.02.03-9 segfault (bug #291559). You wrote hylafax behaves like they are sent ok Do you get a notification that the fax has been successfully sent? What's the state of the send and done queue? Please, send more information and a logfile (syslog) excerpt which shows an attempt to send a fax to the bug tracking system ([EMAIL PROTECTED]). Bodo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291559: analysis
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 build-dep, dpkg- buildpackage -rfakeroot -b. I noticed some compiler warnings ../standard/osmem.h: In function `void* getPtr(tUByte*)': ../standard/osmem.h:98: warning: cast to pointer from integer of different size ../standard/osmem.h: In function `void setPtr(tUByte*, void*)': ../standard/osmem.h:218: warning: cast from pointer to integer of different size I extracted the binaries c2faxsend and c2faxrecv from the package and copied them to /usr/bin. c2faxrecv crashed when receiving a fax. It looks as if C_PLATFORM_64 was defined on my non-64-bit system. To check this I commented out these lines in debian/rules: ifeq ($(DEB_TARGET_ARCH), $(findstring $(DEB_TARGET_ARCH),amd64 ia64 ppc64)) CXXFLAGS += -DC_PLATFORM_64 endif Now I don't get the warnings and c2faxrecv works as expected. (I did not check c2faxsend.) The condition for -DC_PLATFORM_64 seems to be wrong. As a further check I inserted a command for debugging at the dependency build: in debian/rules build: build-stamp echo DEB_TARGET_ARCH = $(DEB_TARGET_ARCH) When making the package it shows that DEB_TARGET_ARCH is empty. Obviously an empty value $(DEB_TARGET_ARCH) must be handled specifically. (Or it's not the right variable to check.) Bodo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291559: capi4hylafax: same problem with version 1:01.02.03-9
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: (900, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages capi4hylafax depends on: ii isdnactivecards 1:3.3.0.20041110-1 support for active ISDN cards and ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libcapi20-2 1:3.3.0.20041110-1 libraries for CAPI support ii libgcc1 1:3.4.3-6 GCC support library ii libstdc++51:3.3.5-8 The GNU Standard C++ Library v3 ii libtiff4 3.7.1-3Tag Image File Format (TIFF) libra -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291559: capi4hylafax: segfault on receive in 1:01.02.03-8 but not 1:01.02.03-7
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 00 00 00 010 logfile capi4hylafax: Feb 02 21:45:19.29: [ 814]: c2faxrecv - INFO: Device "faxCAPI" uses 1 receive thread(s) with the following config: Feb 02 21:45:19.31: [ 814]: c2faxrecv - INFO: Controller=1 : IncomingMSNs=9874994,9874995 Feb 02 21:45:19.31: [ 814]: c2faxrecv - INFO: Started in Hylafax mode and waiting on incoming calls. Feb 02 21:51:18.98: [ 821]: c2faxrecv - INFO: SESSION BEGIN 0095 +49..9874994 Feb 02 21:51:18.98: [ 821]: c2faxrecv - INFO: Incoming speech call on controller 1 to 9874994. Feb 02 21:51:28.35: [ 821]: c2faxrecv - INFO: Connection established. Feb 02 21:51:28.35: [ 821]: c2faxrecv - INFO: BaudRate = 9600 Feb 02 21:51:28.35: [ 821]: c2faxrecv - INFO: Flags = HighRes Feb 02 21:51:28.41: [ 821]: c2faxrecv - INFO: Write fax in path /var/spool/hylafax to file recvq/fax7.tif. [all c2faxrecv processes died] [/etc/init.d/capi4hylafax restart] Feb 02 21:53:47.61: [ 944]: c2faxrecv - INFO: Device "faxCAPI" uses 1 receive thread(s) with the following config: Feb 02 21:53:47.62: [ 944]: c2faxrecv - INFO: Controller=1 : IncomingMSNs=9874994,9874995 Feb 02 21:53:47.62: [ 944]: c2faxrecv - INFO: Started in Hylafax mode and waiting on incoming calls. Feb 02 21:54:12.54: [ 946]: c2faxrecv - INFO: SESSION BEGIN 0096 +49..9874994 Feb 02 21:54:12.54: [ 946]: c2faxrecv - INFO: Incoming speech call on controller 1 to 9874994. Feb 02 21:54:21.93: [ 946]: c2faxrecv - INFO: Connection established. Feb 02 21:54:21.94: [ 946]: c2faxrecv - INFO: BaudRate = 9600 Feb 02 21:54:21.94: [ 946]: c2faxrecv - INFO: Flags = HighRes Feb 02 21:54:21.95: [ 946]: c2faxrecv - INFO: Write fax in path /var/spool/hylafax to file recvq/fax8.tif. [all c2faxrecv died again] -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages capi4hylafax depends on: ii isdnactivecards 1:3.3.0.20041110-1 support for active ISDN cards and ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libcapi20-2 1:3.3.0.20041110-1 libraries for CAPI support ii libgcc1 1:3.4.3-6 GCC support library ii libstdc++51:3.3.5-5 The GNU Standard C++ Library v3 ii libtiff4 3.7.1-2Tag Image File Format (TIFF) libra hylafax-server 1:4.2.1-1 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
