qtwengophone crashed with SIGSEGV in osip_list_add()

Bug #150237 reported by Harry
4
Affects Status Importance Assigned to Milestone
QuteCom
Invalid
Undecided
Unassigned
wengophone (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: wengophone

?

ProblemType: Crash
Architecture: i386
Date: Sun Oct 7 11:41:18 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/qtwengophone
NonfreeKernelModules: vmnet vmmon nvidia
Package: wengophone 2.1.1.dfsg0-4ubuntu1
PackageArchitecture: i386
ProcCmdline: qtwengophone -session 117f000101000119176701900000065850012_1191767661_262582
ProcCwd: /home/harry
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: wengophone
StacktraceTop:
 osip_list_add () from /usr/lib/wengophone/libphapi.so
 __osip_add_nict () from /usr/lib/wengophone/libphapi.so
 osip_transaction_init ()
 eXosip_register () from /usr/lib/wengophone/libphapi.so
 phvlRegister () from /usr/lib/wengophone/libphapi.so
Title: qtwengophone crashed with SIGSEGV in osip_list_add()
Uname: Linux harry-desktop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mythtv netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0xb779b3ed <osip_fifo_tryget+29>: mov 0x4(%edi),%eax
 PC (0xb779b3ed) ok
 source "0x4(%edi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA

Tags: apport-crash
Revision history for this message
Harry (harry81b) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:__osip_add_nict (osip=0x0, nict=0x8b907e8)
osip_transaction_init (transaction=0xb0bfba98, ctx_type=NICT, osip=0x0, request=0x8b5acd8)
eXosip_register (rid=2, registration_period=2940)
phvlRegister (vlid=1) at /build/buildd/wengophone-2.1.1.dfsg0/wifo/phapi/phvline.c:347
owplLineRegister (hLine=20, bRegister=1) at /build/buildd/wengophone-2.1.1.dfsg0/wifo/phapi/phapi.c:636

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in wengophone:
importance: Undecided → Medium
Connor Imes (ckimes)
visibility: private → public
Revision history for this message
Ludovico Cavedon (cavedon) wrote :

Hi, thank you for reporting this problem.

Wengophone has changed its name into qutecom:
https://edge.launchpad.net/ubuntu/+source/qutecom

You can find a binary for intrepid and jaunty in my PPA:
https://edge.launchpad.net/~cavedon/+archive/ppa

Could you please try it and see if you still experience the bug?

Thanks,
Ludovico

Kees Cook (kees)
description: updated
Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The version of Ubuntu your using is in End of Life status. More information may be found at: https://wiki.ubuntu.com/Releases As well, the issue that you reported should be reproducible with the live environment of the Desktop CD development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. In addition, this bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug to the people writing the software. You can learn more about how to do this for various upstreams at https://wiki.ubuntu.com/Bugs/Upstream. Thanks in advance!

Changed in wengophone (Ubuntu):
status: New → Incomplete
Revision history for this message
dino99 (9d9) wrote :

That version has died long ago; no more supported

Changed in wengophone (Ubuntu):
status: Incomplete → Invalid
Changed in qutecom:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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