qtwengophone crashed with SIGSEGV

[Duarte Molha]

Binary package hint: wengophone

it started crahsing after I enabled video calls option (webcam)

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Jul 3 17:03:54 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/qtwengophone
NonfreeKernelModules: nvidia
Package: wengophone 2.1.0.dfsg-3
PackageArchitecture: i386
ProcCmdline: qtwengophone
ProcCwd: /home/duarte
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: wengophone
Stacktrace:
 #0 0xb6748c1c in ?? () from /lib/tls/i686/cmov/libc.so.6
 #1 0xb7ce4d46 in ?? () from /usr/lib/libcurl-openssl.so.4
 #2 0xaffb1c68 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libcurl-openssl.so.4
 ?? ()
 ?? ()
Title: qtwengophone crashed with SIGSEGV
Uname: Linux dudalaptop 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:?? ()
showit (data=0xaffb1c68, type=CURLINFO_TEXT, ptr=0xaffb20a8 "name lookup timed out\n", size=22) at sendf.c:609
Curl_debug (data=0xaffb1c68, type=CURLINFO_TEXT, ptr=0xaffb20a8 "name lookup timed out\n", size=22, conn=0x0) at sendf.c:663
Curl_failf (data=0xaffb1c68, fmt=0xb7d071c1 "name lookup timed out") at sendf.c:261
Curl_resolv (conn=0x14, hostname=0x895fbb8 "x�\223\b0�bx�b�\225\b�\225\b", port=0, entry=0x8ceef2c) at hostip.c:412

[Ludovico Cavedon (cavedon)]

The latest version (2.1.1.dfsg0-4ubuntu1) should have fixed this issue.

Could you please try it and report whether it is working or not?

Thank you!

[Diego (panda84)]

My wengophone crashed with the same error on startup (not using the webcam functionalities).

Could it be similar to bug #139450 ?
https://bugs.launchpad.net/ubuntu/+source/wengophone/+bug/139450

[Diego (panda84)]

mmm... I didn't got the latest version. That's my fault, sorry!

[Diego (panda84)]

I confirm that the latest version solves this problem. I think that new version solves both this bug and bug #139450

[Ludovico Cavedon (cavedon)]

Thank you very much for trying and reporting!

Unfortunately I cannot access bug #139450, because it may contain sensitive data. Could you please mark it as "Fix Release"? Tnx