** Changed in: hylafax (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424250
Title:
Openoffice sendfax hylafax printing impossible under hardy amd64
To
*** This bug is a duplicate of bug 1026919 ***
https://bugs.launchpad.net/bugs/1026919
** This bug has been marked a duplicate of bug 1026919
package hylafax-server 2:6.0.5-5ubuntu1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
--
*** This bug is a duplicate of bug 1026919 ***
https://bugs.launchpad.net/bugs/1026919
** This bug has been marked a duplicate of bug 1026919
package hylafax-server 2:6.0.5-5ubuntu1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
--
*** This bug is a duplicate of bug 1026919 ***
https://bugs.launchpad.net/bugs/1026919
** This bug has been marked a duplicate of bug 1026919
package hylafax-server 2:6.0.5-5ubuntu1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
--
*** This bug is a duplicate of bug 779917 ***
https://bugs.launchpad.net/bugs/779917
** This bug has been marked a duplicate of bug 779917
package hylafax-server 2:6.0.5-5ubuntu1 failed to install/upgrade: el
subproceso instalado el script post-installation devolvió el código de salida
** Bug watch added: Debian Bug tracker #643653
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643653
** Also affects: hylafax (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643653
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Bug watch added: Debian Bug tracker #643653
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643653
** Also affects: hylafax via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643653
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Hi,
you may download 6.0.6-5 packages from Debian and install them on Ubuntu. Start
from page http://packages.qa.debian.org/h/hylafax.html .
Anyway, I do not think this problem has been already corrected there. I
suggest you to report it upstream: http://bugs.hylafax.org/ . Please
provide all
Hi,
you are not forced to install sendmail, but you need an MTA. Would you please
let me know if you have an MTA installed and which one? I would like to know if
hylafax could be changed in order to detect and support your MTA, if any.
Thanks,
Giuseppe
--
You received this bug notification
It seems there are two problems.
First is shown on the very beginning of your log: 396: =: unexpected operator
Second is sendmail missing.
What MTA did you install? postfix? exim? other?
Bye,
Giuseppe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
I believe that -O0 means no optimization at all.
As you may see at the very beginning of
http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html, Without any
optimization option, the compiler's goal is to reduce the cost of
compilation and to make debugging produce the expected results. So
Hi Matthias,
I can certainly provide a patch. Would you sponsor the upload?
Thanks,
Giuseppe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Title:
faxgetty segfault
To manage notifications
Hi Mark,
this is a guess: there are no later Ubuntu releases reporting this error. And
no Debian user reported such a problem.
But 10.04 is LTS, so it should be supported for a lot of years. That's
why I really do not understand why ubuntu developers ignore this
problem. I know Hylafax is not
Hi,
I am still waiting for a reply on the ubuntu developer list for the g++ bug.
Today I sent a second message to the list. If anyone reply, I'll update this
bug report.
Anyway, I do not expect the problem to be present in any other ubuntu
version since the compiler has been fixed in later
** Bug watch added: bugs.hylafax.org/ #941
http://bugs.hylafax.org/show_bug.cgi?id=941
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955013
Title:
g++ compiler error on hylafax source: this
Hi all,
this is a request for help for fixing a bug in g++ compiler shipped with
Lucid.
The problem is shown in bug https://bugs.launchpad.net/bugs/600219 and
it has also shortly reported against g++ as launchpad bug #955013. A
quick summary of the g++ relevant part is also on hylafax bugzilla:
Hi Simon,
I hope it is a line buffered output. I would like to be sure that the logs hit
the disk before the process crashes. Is it creating too much disk I/O? I tough
about putting it in a tmpfs but that would have involved you setting up a file
system for that.
Bye,
Giuseppe
--
You
Hi Yaztromo,
the latest package has standard optimization options (should be -O2). The
source code has been changed in order to create a logfile for each
recvPageDLEData() call. There is no need to run gdb, and I do not have any
estimate on how many log files will be written.
Bye,
Giuseppe
--
Hi all,
I changed the source code in order to create a new logfile in /tmp. This file
contains the this value in many lines of function recvPageDLEData. Could
you please test it and check the new logfile?
Packages are available at
Hi Mark,
this is exactly what hylafax author wrote in
http://bugs.hylafax.org/show_bug.cgi?id=941#c9
Bye,
Giuseppe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Title:
faxgetty segfault
Hi Simon,
I think the No such file is a message from gdb that alert user that gdb does
not find the source file.
Bye,
Giuseppe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Title:
faxgetty
Yes, it should be correct. You do have to manually kill the remaining faxgetty
and run gdb-wrapper again (every time it complete and you want to collect more
information with a new run).
You should also find a log file in /tmp with all required information.
Bye,
Giuseppe
--
You received this
Hi Yaztromo,
the trace is about exactly the same problem I am referring to, so I think this
is not solved at all. I still think the problem being in g++ so I rebuilt all
packages without optimizing at all. They are available at:
Hi Simon,
I try to reply to your questions.
1. The problem about log. The error message is due to this being NULL.
Basically, in C++, you do not address member variable at a fixed
address, so you need a base pointer for your instance (called this)
and then you offset your variable starting at
Hi Yaztromo,
may you confirm that you downloaded packages from
http://eppesuigoccas.homedns.org/~giuseppe/debian/hylafax/lucid-i386/bug%23600219/
instead of
http://eppesuigoccas.homedns.org/~giuseppe/debian/hylafax/lucid-i386/ ?
Thanks,
Giuseppe
--
You received this bug notification because
Hi Yaztromo,
the md5 signatures look correct. I added a README.md5 file in that directory
for future checks.
The dbg files only contains debugging symbols. They are handy for using gdb
on hylafax executables.
I wonder if you have the same problem I am trying to solve, or if this
is a different
So, as hylafax author says in
http://bugs.hylafax.org/show_bug.cgi?id=941#c9 it seems this is a
compiler bug. I rebuilt lucid package using -O flags instead of -O2, as
suggested, and I'll forward this bug to the g++ package for lucid.
Packages are available at
Public bug reported:
Hi,
while getting information about bug #600219 reported against hylafax on
launchpad, I finally understood this is probably a compiler bug. This seems to
be confirmed by hylafax authors in the corresponding bug I opened in hylafax
bugzilla:
This is the bug against gcc: https://bugs.launchpad.net/ubuntu/+source
/gcc-defaults/+bug/955013
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Title:
faxgetty segfault
To manage
Hi, this is probably a side effect of set follow-fork-mode child. gdb only
follow the child process and then, when the fax is received, this child process
ends and a new child is forked from parent.
Can you confirm that when gdb exit, there is still a faxgetty (the parent
process) running?
Hi Deeptht69,
please email me all cores and log files at eppesuig @ debian.org, thanks.
Then, about your questions:
1. /usr/sbin/faxgetty is correctly stripped. All debugging symbols are in files
shipped with *-dbg package. When both packages are installed, you are ok. gdb
knows where to find
Hi Simon,
if you run gdb with faxgetty without -D, does it leave a faxgetty process
running after gdb return?
Thanks,
Giusepp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Title:
faxgetty
Hi Deeptht69,
I had a look at those gdb backtraces. It is quite possible that the problem is
this variable being null. I looked at the sources but I cannot figure out why
this is happening. Nevertheless I did a small change in source file and built
new packages. Could you please install these
Well, I am not a gdb expert, but it could be that gdb change its process name
as the program being traced.
In order to check this, check with command fuser if the logfile in /tmp is
used by faxgetty process. And, with command lsof -p2468, check if this
process uses only faxgetty binary or even
Hi Mark,
why don't you just make faxgetty start (and restart automatically) via
/etc/inittab? Infomation about this configuration are in
/usr/share/doc/hylafax-server/README.Debian.gz
Bye,
Giuseppe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Mark,
thanks for the clarification about how to respawn faxgetty. I will check why
upstart does not restart it in case of errors.
About the other messages you sent, I think there are two problems.
The first one is that you are missing all debug symbols. In order to fix
this, I recompiled the
Hi Mark,
after set logging on on gdb-wrapper.sh, add the following line:
printf 'set follow-fork-mode child\n' $PREFIX.batch
in order to let gdb follow all child processes when there is a fork.
This should let gdb keep waiting all faxgetty processes.
Bye,
Giuseppe
--
You received this bug
Hi,
I just double checked the gdb-wrapper.sh script and spotted two errors. All
lines starting with print should have a \n as end of lines. It happens that
both lines starting with handle do not have such \n. Please add it as here
shown:
printf '# Automatically generated batch\n'
@Simon,
does ps auxfw | grep -C3 faxgetty show gdb?
Bye,
Giuseppe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Title:
faxgetty segfault
To manage notifications about this bug go to:
Hi Mark,
you have perfectly understood. The gdb-wrapper.sh is a command that run your
faxgetty in a way managed by gdb. While your program run, gdb collect a lot of
information in a file named /tmp/gdb-$PID.log, where $PID is the process id of
the sgb-wrapper.sh process. Beside logging
Hi deeptht69 and Simon,
is anyone among you able to use the instructions at:
https://bugs.launchpad.net/ubuntu/+source/hylafax/+bug/600219/comments/15
https://bugs.launchpad.net/ubuntu/+source/hylafax/+bug/600219/comments/21
? This would help a lot in finding the solution for this problem.
I
Il giorno sab, 04/02/2012 alle 13.44 +, Christian Dispas ha scritto:
Hi again, Giuseppe !
I think I followed precisely your kind instructions and, annexed, is the
extract of the terminal after the attempt suggested.
Any idea ? only if you have a spare moment, for which, many thanks in
Thanks for bothering !
I did what you told me and annexed is the reaction of the computer...
You are not executing the commanddpkg on the same directory where you
downloaded both files. The error you read is: ne peut pas accéder à
l'archive: Aucun fichier ou dossier de ce type.
Bye,
Giuseppe
Download these files:
http://centrum.lixper.it/~giuseppe/debian/hylafax/hylafax-client_6.1~20111227-7_amd64.deb
http://centrum.lixper.it/~giuseppe/debian/hylafax/hylafax-server_6.1~20111227-7_amd64.deb
and save them in a directory. Then, at the command line prompt, move to the
same directory and
This bug has been fixed in Debian. Have a look at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655567
You may use the same fix in your hylafax version.
Bye,
Giuseppe
** Bug watch added: Debian Bug tracker #655567
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655567
** Changed in:
Hi Allan, the problem you are reporting now has been fixed yesterday.
The patch may be applied to your version without any problem. Have a
look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655567
Bye,
Giuseppe
** Bug watch added: Debian Bug tracker #655567
Already fixed in 6.0.4
** Changed in: hylafax (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914690
Title:
hfaxd listens on 0.0.0.0 when -l
This bug has been fixed in Debian. Have a look at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655567
You may use the same fix in your hylafax version.
Bye,
Giuseppe
** Bug watch added: Debian Bug tracker #655567
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655567
** Changed in:
Are you using version 2:6.0.3-5.1ubuntu1 of hylafax?
Could you confirm that 172.16.32.65 is an address available to the machine?
What is output of ip addr list?
Thanks,
Giuseppe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What is output of ip addr list?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914690
Title:
hfaxd listens on 0.0.0.0 when -l 172.16.32.65 specified
To manage notifications about this bug go to:
sorry, I didn't see your complete answer. Thanks for the information
provided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914690
Title:
hfaxd listens on 0.0.0.0 when -l 172.16.32.65 specified
To
I cannot reproduce the problem with latest version. Could you please
check if you may install newer version of the packages hylafax-client
and hylafax-server?
You may get them from Ubuntu or Debian, but I am not sure if you may install
these binary package without recompilation.
Try them in this
*** This bug is a duplicate of bug 795188 ***
https://bugs.launchpad.net/bugs/795188
** This bug is no longer a duplicate of bug 804557
package hylafax-client 2:6.0.5-5ubuntu1 failed to install/upgrade:
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
**
*** This bug is a duplicate of bug 795188 ***
https://bugs.launchpad.net/bugs/795188
** This bug has been marked a duplicate of bug 795188
package hylafax-client 2:6.0.5-5ubuntu1 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned error exit
*** This bug is a duplicate of bug 795188 ***
https://bugs.launchpad.net/bugs/795188
** This bug has been marked a duplicate of bug 795188
package hylafax-client 2:6.0.5-5ubuntu1 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned error exit
** Changed in: hylafax (Ubuntu)
Status: New = Confirmed
** Also affects: hylafax (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796774
** Changed in: hylafax (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798863
Title:
package hylafax-server-dbg 2:6.0.5-5ubuntu1 failed to install/upgrade:
*** This bug is a duplicate of bug 795188 ***
https://bugs.launchpad.net/bugs/795188
** This bug has been marked a duplicate of bug 795188
package hylafax-client 2:6.0.5-5ubuntu1 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned error exit
Hi Manuel,
Thunderbird is not an MTA (Mail Transfer Agent), but an MUA (Mail User Agent).
Please refer to these pages
http://en.wikipedia.org/wiki/Message_transfer_agent
http://en.wikipedia.org/wiki/Email_client
Please check if file /usr/lib/sendmail is present on your system and
also type this
There seems to be two problems shown in your logs.
First one is about an error while stopping hylafax. Was hylafax already
installed? (Is this un upgrade or a new install?)
Second (and fatal) is about executable /usr/lib/sendmail missing. Could
you check if this executable is present? What MTA
*** This bug is a duplicate of bug 799317 ***
https://bugs.launchpad.net/bugs/799317
** This bug has been marked a duplicate of bug 799317
package hylafax-server (not installed) failed to install/upgrade: il
sottoprocesso vecchio script di post-installation ha restituito lo stato di
*** This bug is a duplicate of bug 798863 ***
https://bugs.launchpad.net/bugs/798863
** This bug has been marked a duplicate of bug 799090
package hylafax-server (not installed) failed to install/upgrade: el
subproceso instalado el script post-installation devolvió el código de salida
de
*** This bug is a duplicate of bug 798863 ***
https://bugs.launchpad.net/bugs/798863
** This bug is no longer a duplicate of bug 799317
package hylafax-server (not installed) failed to install/upgrade: il
sottoprocesso vecchio script di post-installation ha restituito lo stato di
errore
*** This bug is a duplicate of bug 798863 ***
https://bugs.launchpad.net/bugs/798863
the problem you reported has its roots on the missing sendmail
executable. The error message is:
FATAL ERROR: /usr/lib/sendmail does not exist or is not an executable
program!
Could you check if you have
The error is related to a missing MTA:
FATAL ERROR: /usr/lib/sendmail does not exist or is not an executable
program!
Could you please check what MTA is installed on this system?
Thanks,
Giuseppe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 549493 ***
https://bugs.launchpad.net/bugs/549493
** This bug has been marked a duplicate of bug 549493
package hylafax-client 2:6.0.3-5.1ubuntu1 failed to install/upgrade: cp:
`/etc/hylafax/pagesizes' and `/var/spool/hylafax/etc/pagesizes' are the same
Sure, MTA is a program that transfer email messages, like sendmail,
exim, postfix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798863
Title:
package hylafax-server-dbg 2:6.0.5-5ubuntu1 failed to
*** This bug is a duplicate of bug 783654 ***
https://bugs.launchpad.net/bugs/783654
Hi,
as show in your log, it seems you are facing a well known problem:
Setting up hylafax-client (2:6.0.5-5ubuntu1) ...
cp: `/etc/hylafax/pagesizes' and `/var/spool/hylafax/etc/pagesizes' are
the same file
*** This bug is a duplicate of bug 783654 ***
https://bugs.launchpad.net/bugs/783654
** This bug has been marked a duplicate of bug 783654
package hylafax-client 2:6.0.3-5.1ubuntu1 failed to install/upgrade:
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
*** This bug is a duplicate of bug 783654 ***
https://bugs.launchpad.net/bugs/783654
** This bug has been marked a duplicate of bug 783654
package hylafax-client 2:6.0.3-5.1ubuntu1 failed to install/upgrade:
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
*** This bug is a duplicate of bug 783654 ***
https://bugs.launchpad.net/bugs/783654
** This bug has been marked a duplicate of bug 783654
package hylafax-client 2:6.0.3-5.1ubuntu1 failed to install/upgrade:
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Public bug reported:
Binary package hint: samba
Hi,
I just installed a 10.10 i386 Ubuntu and integrated it with a Windows AD
domain. After reboot I cannot log in anymore to the system using my AD
credentials because winbind does not start automatically.
I think the problem is probably a
** Description changed:
- Binary package hint: samba
+ Binary package hint: winbind
Hi,
I just installed a 10.10 i386 Ubuntu and integrated it with a Windows AD
domain. After reboot I cannot log in anymore to the system using my AD
credentials because winbind does not start
Public bug reported:
Binary package hint: samba
Hi,
I just installed a 10.10 i386 Ubuntu and integrated it with a Windows AD
domain. After reboot I cannot log in anymore to the system using my AD
credentials because winbind does not start automatically.
I think the problem is probably a
** Description changed:
- Binary package hint: samba
+ Binary package hint: winbind
Hi,
I just installed a 10.10 i386 Ubuntu and integrated it with a Windows AD
domain. After reboot I cannot log in anymore to the system using my AD
credentials because winbind does not start
Simon,
you should get packages from Debian and rebuild them. I am unsure if you may
install them as they are. They might work. If you get any problem while
installing them via dpkg, then you'll ha ve to rebuild them.
In Debian you will find two more packages with names ending in -dbg,
that
Hi,
this bug reports about many different problems. The only way to fix each of
them is to supply all information using a debugger as explained in comments
#15, #21, and #23. If you may produce that data, then problably you bug will be
found and fix.
You may add your data to this report or you
Hi Andreas,
I received a good news a few hours ago. An ubuntu user told me that Natty
packages are working fine on Ubuntu 10.10. Could you try them (and install also
-dbg package in order to get gdb traces eventually)?
Thanks,
Giuseppe
--
You received this bug notification because you are a
Hi Andreas, check comment #23 for a few instruction about debugging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Title:
faxgetty segfault
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 549493 ***
https://bugs.launchpad.net/bugs/549493
** This bug has been marked a duplicate of bug 549493
package hylafax-client 2:6.0.3-5.1ubuntu1 failed to install/upgrade: cp:
`/etc/hylafax/pagesizes' and `/var/spool/hylafax/etc/pagesizes' are the same
*** This bug is a duplicate of bug 549493 ***
https://bugs.launchpad.net/bugs/549493
** This bug is no longer a duplicate of bug 664902
package hylafax-client 2:6.0.3-5.1ubuntu1 failed to install/upgrade:
** This bug has been marked a duplicate of bug 549493
package hylafax-client
*** This bug is a duplicate of bug 549493 ***
https://bugs.launchpad.net/bugs/549493
** This bug has been marked a duplicate of bug 549493
package hylafax-client 2:6.0.3-5.1ubuntu1 failed to install/upgrade: cp:
`/etc/hylafax/pagesizes' and `/var/spool/hylafax/etc/pagesizes' are the same
*** This bug is a duplicate of bug 549493 ***
https://bugs.launchpad.net/bugs/549493
** This bug has been marked a duplicate of bug 549493
package hylafax-client 2:6.0.3-5.1ubuntu1 failed to install/upgrade: cp:
`/etc/hylafax/pagesizes' and `/var/spool/hylafax/etc/pagesizes' are the same
** Changed in: hylafax (Ubuntu)
Status: Fix Committed = Confirmed
--
faxgetty segfault
https://bugs.launchpad.net/bugs/600219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: bugs.hylafax.org/ #941
http://bugs.hylafax.org/show_bug.cgi?id=941
** Also affects: hylafax via
http://bugs.hylafax.org/show_bug.cgi?id=941
Importance: Unknown
Status: Unknown
--
faxgetty segfault
https://bugs.launchpad.net/bugs/600219
You received this bug
Is this a duplicate of bug #549493?
--
package hylafax-client 2:6.0.3-5.1ubuntu1 failed to install/upgrade:
https://bugs.launchpad.net/bugs/664902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It seems this is a duplicate of a known problem. Could you check bug #549493 in
launchpad?
If it is the same problem, then this should fix the problem:
# invoke-rc.d hylafax stop
# dpkg --configure hylafax-client hylafax-server
--
package hylafax-server 2:6.0.4-10ubuntu1 failed to
Hi all,
I just uploaded a new hylafax package, version 6.0.5-4, with two new binary
packages with debugging symbols for client and server. They are currently
sitting in the NEW queue for Debian, since they require manual approval for
those new binary packages. Once approved it should migrate
*** This bug is a duplicate of bug 476098 ***
https://bugs.launchpad.net/bugs/476098
** This bug has been marked a duplicate of bug 476098
package hylafax-server (not installed) failed to install/upgrade: subprocess
installed post-removal script returned error exit status 1
* You can
Hi Mike, could you please check it using gdb, as explained on previous
messages on this bug report?
Thanks,
Giuseppe
--
faxgetty segfault
https://bugs.launchpad.net/bugs/600219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
If you follow instruction on http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=553027#15 then you should find them in
/tmp/faxsend-*
--
faxgetty segfault
https://bugs.launchpad.net/bugs/600219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Mike, you are right! I didn't mean to use faxsend script for faxsend, bug
faxgetty.
In should «killall faxgetty», download the general scrip gdb-wrapper.sh from
thttp://people.ifax.com/~aidan/hylafax/gdb/ and run it with args ttyS0 (or
the device name your modem is available).
--
faxgetty
Francesco,
another (simpler) way to check it using gdb is to follow this instruction
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553027#15
Bye,
Giuseppe
** Bug watch added: Debian Bug tracker #553027
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553027
** Also affects: hylafax
[I will ask something somewhat peculiar, I hope not so difficult to execute]
Could you check if you may get any core dumped from faxgetty? Usually segfault
would create such file is ulimit does not forbid it.
ulimit is specified in /etc/security/limits.conf, you should add to that file
two
Hi, this seems to be same problem all hylafax have when upgrading from
6.0.3 as shipped with Lucid. Please stop hylafax by hand before
upgrading it. Please check that no /var/spool/hylafax/etc is still
mounted after stopping hylafax; if it is then unmount it before updating
hylafax.
--
package
I believe that the problem here is that Ubuntu took a broken version
from Debian and released it. The Version for Debian stable doesn't
present this prolem, so this cannot be fixed in Debian package. What I
suggest to Ubuntu developers is to change the init.d file from any 6.0.4
or 6.0.5 Debian
In order to collect more information, could you change ServerTracing and
SessionTracing to 8, restart hylafax, produce the error, and then send the
relevant log from /var/log/daemon and/or /var/log/messages ?
Thanks
--
faxgetty segfault
https://bugs.launchpad.net/bugs/600219
You received
Hi,
could you please better explain how you play such file? What command options
are you giving?
--
Faxsend crashes while trying to play file
https://bugs.launchpad.net/bugs/638789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
In order to collect more information, could you change ServerTracing and
SessionTracing to 8, restart hylafax, produce the error, and then send the
relevant log from /var/log/messages ?
Thanks
--
Faxsend crashes while trying to play file
https://bugs.launchpad.net/bugs/638789
You received
Do you have the same result using hylafax 6.0.4-10ubuntu1 from maverick?
--
Faxsend crashes while trying to play file
https://bugs.launchpad.net/bugs/638789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
1 - 100 of 155 matches
Mail list logo
