GNOME Bugzilla – Bug 579271
ekiga crashed with SIGSEGV in GMVideoInputManager_ptlib::OPEN
Last modified: 2009-08-06 20:55:46 UTC
Binary package hint: ekiga i just opened ekiga from cli to test my webcam driver (http://ubuntuforums.org/showthread.php?p=5451750) and it coredump traces on https://bugs.launchpad.net/bugs/362804 $ apt-cache policy ekiga ekiga: Installed: 3.2.0-0ubuntu1 Candidate: 3.2.0-0ubuntu1 Version table: *** 3.2.0-0ubuntu1 0 500 ftp://darkstar.ist.utl.pt jaunty/main Packages 500 ftp://archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ProblemType: Crash Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/ekiga NonfreeKernelModules: nvidia Package: ekiga 3.2.0-0ubuntu1 ProcCmdline: ekiga ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 Signal: 11 SourcePackage: ekiga StacktraceTop: GMVideoInputManager_ptlib::open () Ekiga::VideoInputCore::internal_open () Ekiga::VideoInputCore::start_preview () Ekiga::VideoInputCoreConfBridge::on_property_changed sigc::internal::slot_call2<sigc::bound_mem_functor2<void, Ekiga::VideoInputCoreConfBridge, std::string, _GmConfEntry*>, void, std::string, _GmConfEntry*>::call_it () Title: ekiga crashed with SIGSEGV in GMVideoInputManager_ptlib::open() Uname: Linux 2.6.28-12-generic x86_64 UserGroups: adm admin cdrom davfs2 dialout dip fax floppy fuse kvm lpadmin nagios netdev plugdev polkituser sambashare scanner sudo sys syslog tape users video voice www-data
Can you get a better backtrace?
(In reply to comment #1) > Can you get a better backtrace? You mean with debug symbols? if so, the launchpad retracers already have them https://bugs.edge.launchpad.net/ubuntu/+source/ekiga/+bug/362804/comments/4 plus i just tried to run ekiga with kernel Linux blubug 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux and it run fine (opened unlike last time), but still generated a .crash file
Well, I had hoped for a more refined backtrace :-/ is it easy to reproduce?
i can open it now without crashing. still when I close it, CLI always says Segmentation fault, but no .crash is being generated
That crash on exit is another issue entirely. Since the bug doesn't seem to have reappeared, I'll close that report. Feel free to reopen if you get it again.
the downstream report contains a backtrace: ".
+ Trace 215460
Thread 10 (process 24270)
Thread 9 (process 24269)
Thread 1 (process 24224)
Snark, is the trace above a valid one? Best regards, Yannick