[apport] ekiga crashed with SIGSEGV in PHostByName::GetHost()

Bug #82426 reported by hawkes
28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ekiga (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: ekiga

I'm not even sure, that i have started ekiga. The crashtool appeared suddenly, after 5s after Gnome login. Hope this helps,

ProblemType: Crash
Date: Wed Jan 31 08:14:42 2007
Disassembly: 0x0:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/ekiga
Package: ekiga 2.0.3-0ubuntu5
ProcCmdline: ekiga
ProcCwd: /home/hawkes
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: ekiga
StacktraceTop:
 ?? ()
 PHostByName::GetHost ()
 PHostByName::GetHostAddress ()
 PIPSocket::GetHostAddress ()
 OpalInternalIPTransport::GetIpAndPort ()
Uname: Linux ela 2.6.20-5-generic #2 SMP Sat Jan 6 09:44:32 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip lpadmin plugdev scanner video

Revision history for this message
hawkes (hawkes) wrote : Dependencies.txt
Revision history for this message
hawkes (hawkes) wrote : ProcMaps.txt
Revision history for this message
hawkes (hawkes) wrote : ProcStatus.txt
Revision history for this message
hawkes (hawkes) wrote : Registers.txt
Revision history for this message
hawkes (hawkes) wrote : Stacktrace.txt
Revision history for this message
hawkes (hawkes) wrote : ThreadStacktrace.txt
Changed in ekiga:
importance: Undecided → Low
status: Unconfirmed → Confirmed
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Stephen Cook (siti) wrote :

Are you able to test if this problem occurs with ekiga in gutsy? The gutsy release contains a new ekiga which fixes a lot of problems.

Changed in ekiga:
status: Confirmed → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

The backtrace is similar to http://bugzilla.gnome.org/show_bug.cgi?id=364480 which has been marked fixed, doing the same with the distribution task, feel free to reopen if you still get the bug though

Changed in ekiga:
status: Incomplete → Fix Released
Changed in gnomemeeting:
status: Unknown → Fix Released
Revision history for this message
hawkes (hawkes) wrote :

Yes, this bug still occurs in GUTSY. Opening Ekiga, it registers itself, Closing Egika. After about 5-10seconds the Crash Dialog comes up. I'm not sure, how to attach the new backtrace to this bug.

Revision history for this message
encompass (encompass) wrote :

I also get this in gutsy. But this is after the system tells me I have no audio device to use. I click ok... then it hang with the button down for a while and then give me apport to report the bug.

Revision history for this message
ThomasWG (twg) wrote : Crashes without warning.

09:31:38 Started Ekiga 2.0.11 for user work
09:31:56 Set STUN server to stun.ekiga.net (Port Restricted NAT)
09:32:03 Registered to xx.xxx.xxx.245
10:26:05 Registered to xx.xxx.xxx.245
11:20:41 Registration failed: Timeout
11:26:41 Registration failed: Timeout
11:33:11 Registration failed: Timeout
11:40:41 Registration failed: Timeout
11:48:41 Registration failed: Timeout
11:57:41 Registration failed: Timeout
12:08:11 Registration failed: Timeout
12:19:11 Registration failed: Timeout
12:31:41 Registration failed: Timeout
12:45:41 Registration failed: Timeout

This is the 3rd or 4th time I have submitted a bug report and the program is still crashing without warning. I do not get a message pop up it just does not work. I work at home and I go to use the phone and it will not dail, I don't even get a dail tone sound. When i open the General History this is what I get. At first I thought it was related to the alsa driver, because it use to crash if I opened a music/audio program. But now I am opening nothing and I am getting the same errors.

Changed in gnomemeeting:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.