** Changed in: hylafax (Debian)
Status: Incomplete => 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/600219
Title:
faxgetty segfault
To manage notifications about this bug go to:
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
Could some explain what O0 does? From the man pages:
"Reduce compilation time and make debugging produce the expected
results. This is the default. "
So is that same as not using -O at all? Or is it the same as just -O, or
something entirely different?
--
You received this bug notification beca
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 a
** Changed in: hylafax
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/600219
Title:
faxgetty segfault
To manage notifications about this bug go to:
https://b
see as well 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 notifications about this bug go to:
https://bugs.launchpad.net/hylafax/+bug/600219/+su
I would suggest fixing this by building the problematic file with -O0.
Can you provide such a patch for hylafax?
--
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 man
Giuseppe:
I see your point. My hylafax server is running on a computer dedicated
to that function. I am looking forward to upgrading to 12.04 LTS
specifically because of this bug.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
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 inc
Giuseppe:
Do we know that this bug is no longer present in the g++ compiler that
will ship with 12.04? If that's the case, I'll just wait it out,
running the un-optimized packages, until 12.04 is released. There's no
point in chasing a bug that's already been squashed!
Mark
--
You received th
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 versi
Yaztromo:
I looks as though nobody has seen any segfaults with the completely un-
optimized packages? I am coming up on a week of running un-optimized
packages without any segfaults, though it took 8 days to catch one when
I was running the "-O" packages. I will have to run unoptimized right
up
I left the logging going for a few more days. But even though I had
several segfaults, the value for 'this' never showed anything different.
So I then reverted to the completely unopitimised package, not having
any segfaults since.
Can we cautiously say the fix has been found then? If the answer i
Any new developments with this bug? I have not (yet) installed the
"enhanced logging" packages, as it seemed from Yaztromo's message that
they may not be providing the required information. As before, I am
running the non-optimized packages, and have not yet had another
segfault. If it will help
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 received
Guiseppe,
Did you flush(fd) the logging every time you log something? Writing to a
file is heavily asynchronous.
Simon
--
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
Well I already got a segfault with the new packages. However the log
doesn't look like its recorded the final of this before the crash.
** Attachment added: "hylafax-XX.log"
https://bugs.launchpad.net/ubuntu/+source/hylafax/+bug/600219/+attachment/2940186/+files/hylafax-XX.log
--
Yo
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
--
Ok Guiseppe, will do.
Is this packages unoptimised? No -O?
Do I need to run with gdb to get the log in tmp?
Welcome aboard the unoptimised train Mark! So far so good here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
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
http://eppesuigoccas.homedns.org/~giuseppe/debian/hylafax/luc
BAD NEWS!!!
After going for 8 days without a problem, I just had 3 segfaults back-
to-back! All occurred before the originating phone number was logged,
so I can't tell if they were all from the same sender. The last fax
received before the segfaults was from the sender that was causing
problems
Hi Deep,
I've been wondering the same too, and the only difference I can find is
that Athlon supports SSE and Duron doesn't. Does -O enable SSE support?
I don't know anything about gcc but would've thought enabling SSE would
need a seperate flag.
A mystery!
--
You received this bug notification
yaztromo:
Glad to hear your setup is working. I am now at 8 days of continuous
running without a segfault, using the "-O" compiled packages. I wonder
why the "-O" compiled packages didn't work for you? Hardware
difference? (My fax server uses an AMD Athlon CPU). Anyway, I hope
this is the end
I'm going to tentatively say that the no optimisations package is bug
free.
Two days running and no segfaults. Normally I would have one or two by
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/60
Simon:
Good points. As I said earlier, back when I was having segfaults, these
patterns emerged: 1) segfaults were very common when receiving from one
particular sender, 2) when a segfault occurred from the problem sender,
the sender would automatically try to send the fax again. It would
ofte
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:
faxgett
Hi Mark, hi Guiseppe,
Yes, sure, we are all on one line here. And Mark, in my mind there is no
doubt that "if (log) {" is not causing the problem. And yes, the this
pointer is damaged some other way. BUT if this would be due to a
compiler issue I have trouble to accept that this happens only once
I was just browsing the source code for ModemServer.c++, and I notice
that ModemServer::vtraceStatus is called by ModemServer::traceStatus,
which has, as one of its arguments, a variable length format string. It
makes me wonder if the format string trailing NULL is what's clobbering
the "this" poi
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
To
Simon:
I'm not a compiler expert, but it seems to me that "the offending code"
being executed is only a problem when some other process has previously
clobbered the "this" pointer. The offending code itself is probably
fine, but somewhere, perhaps in some data buffer management process
elsewhere,
I have reached one week since installing the "-O" packages. 77 faxes
have been received during that time, with no segfaults. The OTHER
problem I was having (the computer occasionally freezing until the mouse
is moved) also seems to be fixed. I hope everything continues to work
when I install Ubu
Hi All,
Thank you all for your input. I'll put a bit more detail in: The RTC means
Return To Command (mode). What I know about faxes is that they start up and
negotiate how they are going to do "it". So the exact protocol, page size, and
transfer speed are agreed. This happens with a bi-directi
Adding my two cents.
As yaztromo says, segfaults seem to be more likely when the fax is
originating from a particular sender. However, for me, when the
"problem sender" would try to re-send the same fax, it could segfault in
a different place each time. This would suggest that it is nothing
I was thinking maybe the crash is only triggered one in every x faxes
because most of the time the bad compiled code is not touched upon
often. Possibly in this case it is "Adjusting for RTC (real time clock?)
found at row" in "recvPageDLEData". Maybe this does not happen often,
and when it does, t
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
Giuseppe,
I have been digging into the 6.0.5 code using the input Yaztromo
provided with the SEGVIO he logged. And I would like to make two
statements and have your view on them:
1. I found that the actual code on that famous line 950 is just if
(log) { although this "log" could be a ha
Giuseppe:
Just to confirm, I am coming up on one week since installing the "-O"
compiled packages with no segfaults so far. Could this bug be depending
on the CPU type? My system is also an AMD processor, but a more recent
one. (Athlon, maybe?)
Anyway, I'm hoping I've seen my last segfault.
Ma
Installed and running :) Let's see!
Just for reference my CPU specs and kernel in case they are the problem.
Linux Shula 2.6.32-39-generic-pae #86-Ubuntu SMP Mon Feb 13 23:05:11 UTC
2012 i686 GNU/Linux
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 3
mod
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:
http://eppesuigoccas.homedns.org/~giuseppe/debian/hylafax/lucid-i386
Picked up a segfault!
** Attachment added: "gdb-30003.core"
https://bugs.launchpad.net/ubuntu/+source/hylafax/+bug/600219/+attachment/2909836/+files/gdb-30003.core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "gdb-30003.log"
https://bugs.launchpad.net/ubuntu/+source/hylafax/+bug/600219/+attachment/2909855/+files/gdb-30003.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600219
Tit
Now we wait...
http://www.youtube.com/watch?v=lfa8fC93Pds
(I am Dutch)
--
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:
Okay got you. I wrote a small script to respawn gdb everytime a fax is
received, this also can mitigate against unexpected segfault.
#!/bin/bash
cd /root
while [ 0 ] ; do
if ! ps ax | grep [g]db > /dev/null; then
echo "Could not detect gdb starting a new process"
killall 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 b
Giuseppe, I have attempted to run faxgetty via gdb with these steps:
- Install all packages from bug directory including dbg packages.
- Download gdb wrapper and add your fixes + suggested lines.
- From a local tty run "./gdb-warpper.sh /usr/sbin/faxgetty ttyS0"
However after reception of first
I am half way through our "busy day" at the office, using the "-O"
hylafax-*_6.0.5-5_i386.deb packages (same md5sums as listed in message
#84). So far today, we have received over 25 faxes, and no segfaults
since the packages were installed last week. This is a longer time/more
faxes without a se
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
Thanks Giuseppe. The debs I used are still sat on the server. Here are
the md5's. They appear to check out against the ones in your bug
directory, but I would be grateful if you could check I'm not going
crazy.
MD5(hylafax-client_6.0.5-5_i386.deb)= 6c03cb2126ef70ea5953f22f768fc39a
MD5(hylafax-ser
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
Sorry, but this one is segfaulting already. Falling back to hardy
packages again.
Mar 19 13:21:17 Shula kernel: [249718.200222] faxgetty[27670]: segfault
at a3c ip 0805baf0 sp bfc3c180 error 4 in faxgetty[8048000+6f000]
Sorry I can't be of more help, but it's hard to debug while at work and
on a
Packages installed, Guiseppe.
Will report back midweek, it would have definitely segfaulted by then.
--
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 notific
I installed the new packages yesterday. So far, no segfaults. Will
keep watching and waiting
--
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 notificati
Giuseppe:
I'm not in my office today, but if I have time tomorrow I'll install the
new packages and let you know if anything has changed. It may take a
week or more to determine if the segfaults are gone. Thanks for all your
effort!
Mark
--
You received this bug notification because you are a
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 notification
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
http://eppesuigoccas.homedns.org/~giu
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
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 s
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 All,
I had faxgetty running in gdb, as I posted previously. In my case, faxgetty
keeps receiving faxes, but "frees" itself of gdb. Maybe it is the same as
Deepht69 describes in #69.
I now started faxgetty without the -D option. I do not mind if it sticks to my
terminal. We'll see if faxgetty
Late breaking news:
I just had a series of segfaults, which has generated 2 ".core" files,
each 878000 bytes long, each with a log file about 4500 bytes long.
Here is one of the log files:
root@isabel:/tmp# cat gdb-9574.log
[New process 9580]
Program received signal SIGSEGV, Segmentation fault
I have received a few more faxes with gdb running, but no segfaults so
far.
As before, gdb exits after each fax is received, and must be manually
re-started. The log file for a normally received fax reads:
root@isabel:/tmp# cat gdb-9245.log
[New process 9251]
[New process 9304]
Program exited
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?
Ab
Perhaps it is not so easy
gdb seems to exit as soon as a fax is received, even when it does not
cause a segfault. Here is the log after it exits:
toor@isabel:~$ cat /tmp/gdb-4945.log
[New process 4951]
[New process 5045]
Program exited normally.
No stack.
/tmp/gdb-4945.batch:12: Error in
OK, I just installed the hylafax 6.0.5 deb packages on my Ubuntu 10.04
system, and ran "gdb-wrapper.sh faxgetty -D ttyS0" Now, my process tree
shows:
root@isabel:/tmp# ps auxw|grep fax
uucp 3839 0.0 0.2 4820 1568 ?S17:01 0:00
/usr/sbin/hfaxd -d -i 4559
uucp 4251 0.1
Hi Guiseppe and Mark,
Following the instructions from Guiseppe (who said you were not an
expert on gdb?!) , I changed the gdb-wrapper. Now all seems to work! gdb
starts up, blocking the console and in the process list I can now see
both gdb running and faxgetty. Like this:
simon@Helios:~$ ps auxf
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
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 6.0
Giuseppe:
> 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
Recent versions of Ubuntu no longer use the "/etc/inittab" system. The
current method is to have a file
Giuseppe:
I don't know if this is a problem or not.
I killed "faxgetty", then executed "gdb-wrapper.sh
/usr/local/sbin/faxgetty -D ttyS0". Faxgetty once again appears in the
process tree, but the log at /tmp/gdb-24080.log reads:
Program exited normally.
No stack.
/tmp/gdb-24080.batch:11: Error
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 subscrib
Giuseppe/Simon:
I was not in my office yesterday, so I haven't yet tried the repaired
"gdb-wrapper.sh" script.
Looking at the log files, there were 2 segfaults: one was from a number
different from the one that has been causing all of the segfaults to
date, and the other occurred on the first pag
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 ev
Hi Giuseppe,
No, it does not show gdb:
simon@Helios:/usr/lib$ ps auxfw | grep -C3 faxgetty
root 2602 0.0 0.1 3164 1780 pts/2Ss 20:58 0:00 \_ login
-h antarctica.local -p
simon 2666 0.0 0.3 6068 3324 pts/2S20:58 0:00 \_
-bash
simon 3926 0.0
@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:
http
Deep,
To answer your question earlier. I am running the 8.04 packages in
10.04.
--
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
Mark, Giuseppe,
In the past I have been putting some effort in, so I returned to find
out where I stalled. Amongst the trouble I ran into was that I am
running hylafax version 6.0.3 but I downloaded the source of 6.0.5 for
debugging. And it did not work. So later I loaded the 6.0.3 version
also. B
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'
Giuseppe:
Problem: I renamed "/etc/init/ttyS0.conf" to prevent faxgetty from respawning,
then re-booted.
I ran gdb-wrapper.sh faxgetty ttyS0, but no faxgetty or gdb appeared in the
list of processes. The logs in /tmp/gdb-1565.log say exactly this:
/tmp/gdb-1565.batch:6: Error in sourced comma
Giuseppe:
Just to make sure I have this right: When I try to kill faxgetty, it
immediately respawns. There is an entry in "/etc/init/" named
"ttyS0.conf", which contains:
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /usr/local/sbin/faxgetty ttyS0
I will change t
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 informati
Giuseppe: Some more info that may be helpful: I have reviewed my
"/var/log/syslog" files, and have discovered that the faxgetty segfault
only occurs when receiving a fax from one particular sender. Of the
last 9 faxes received from that sender, 4 came thru OK, and 5 produced
segfaults before bei
Giuseppe: I will be happy to set up my system to generate debugging
traces for you. I will also be paying close attention to when the error
occurs. As I said, it seems that one particular sender seems to
generate the error, but that could just be confirmation bias. After
getting a segfault after
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 would
Hi deep,
I was surprised by your remark that you were able to see something of
the fax. I have tried that many times, in an attempt to see "who did it"
but I was never able to see a fax. The most recent failure I had here
was from March 1st, and indeed, after changing the rights from 0600 to
0644
I am trying to run a hylafax server in my office, and am getting tripped
up by this same bug. My computer is running Desktop Ubuntu 10.04.4 LTS.
I have tried 2 different serial modems with no difference noted. I
compiled hylafax 6.05 from source, but this did not help.
The segfault seems to occu
I did this in PHP and run it as root in /etc/crontab
PHP:
Edit /etc/crontab and add:
#runfaxgetty .php runs every hour
01 ** * * rootphp -f /runfaxgetty.php
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Hi Nancy (et Al)
I have been investing some time in an attempt to corner this problem.
What I did:
= Downloading the latest version of Hylafax only to find out my box is
running an older version.
= Downloading the right version and trying to compile it. Then you find
out that the shared libra
Did we ever find a solution to this? Running 10.04.2 LTS. Would greatly
appreciate a patch.
In the mean time, could anyone provide a script that watches the logs
for faxgetty to crash and restarts hylafax or faxgetty when this
happens? I am not much of a wizard.
--
You received this bug notifica
@Simon
We receive about 30 faxes per day. During the time I was running the
Lucid version of Hylafax I would see faxgetty segfault at least twice or
more each day. So in my opinion it would appear to be related to how
often you receive a fax.
You can find some logs I made at the time further up.
Gents,
In the meanwhile I tried to download and compile the package. No problem with
that.
Since I do not want to install it I ran into the problem that some shared lib
is missing. Apparently I downloaded the source of an other version than I am
running now. I'll re-check and have another try.
Like Francesco said, I just downgraded to the 8.04 version. You can then
hold the package from upgrading using dpkg or aptitude. This has been
the situation for me since the release of lucid.
Alternatively you can install the Debian version which also seems
unaffected. Which leads me to think that
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 inclu
Giuseppe,
I have tried the wrapper but it seems not to work. So I tried to jest run the
gdb command found in the wrapper from the command line and found that gdb
complains that it does not have debugging symbols. I am sorry but I have little
experience with debugging with gdb.
I think I have to
Gentlemen,
Thank you for your prompt response. I did not subscribe to this topic,
so I am a bit late reacting, sorry. I am happy to see commitment here.
@Giuseppe: I will run faxgetty in the wrapper and get back here with
results. Although I should be able to dig down into the
Hi
I am running 10.04 server on a 32-bit pc, and everything is running
flawlwssly, my previous problem was an intermittent hardware one.
Cheers
Antonio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
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
On Tue, 15 Mar 2011 12:33:30 -, "Simon G. Stikkelorum"
<600...@bugs.launchpad.net> wrote:
> Can I please ask for the situation at this moment? I am running a
> fully updated server Ubuntu 10.04 Linux 2.6.32-29 and still have the
> problem.
> Thank you
>
> Simon
Because of this bug (opened sev
Can I please ask for the situation at this moment? I am running a fully updated
server Ubuntu 10.04 Linux 2.6.32-29 and still have the problem.
Thank you
Simon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: hylafax
Importance: Unknown => Medium
--
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
ubuntu-bugs@lists.ubuntu.com
https
Hello Giuseppe,
seems like I have found the problem. While testing, I did
disable ECM on the Cisco gateway (dial-peer). After re-
enabling ECM everything does work as expeceted.
Thanks
Andreas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
1 - 100 of 136 matches
Mail list logo
