After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 366174 - crash in Ekiga Softphone: setting up creative webc...
crash in Ekiga Softphone: setting up creative webc...
Status: RESOLVED DUPLICATE of bug 376078
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-28 09:13 UTC by rpage_is_king
Modified: 2007-01-14 18:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description rpage_is_king 2006-10-28 09:13:33 UTC
Version: 2.0.3

What were you doing when the application crashed?
setting up creative webcam notebook pro with driver gspca. Crashed on first run.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 103043072 vsize: 0 resident: 103043072 share: 0 rss: 26849280 rss_rlim: 0
CPU usage: start_time: 1162026679 rtime: 0 utime: 414 stime: 0 cutime:235 cstime: 0 timeout: 179 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/ekiga'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1246882128 (LWP 8797)]
[New Thread -1294767200 (LWP 8858)]
[New Thread -1294091360 (LWP 8851)]
[New Thread -1293825120 (LWP 8829)]
[New Thread -1293558880 (LWP 8828)]
[New Thread -1293263968 (LWP 8822)]
[New Thread -1310049376 (LWP 8813)]
[New Thread -1249080416 (LWP 8802)]
[New Thread -1248814176 (LWP 8801)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 3 (Thread -1294091360 (LWP 8851))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PHashTable::Table::GetElementAt
    from /usr/lib/libpt.so.1.10.2
  • #5 PAbstractDictionary::AbstractSetAt
    from /usr/lib/libpt.so.1.10.2
  • #6 V4LNames::PopulateDictionary
    from /usr/lib/pwlib/device/videoinput/v4l_pwplugin.so
  • #7 V4LNames::Update
    from /usr/lib/pwlib/device/videoinput/v4l_pwplugin.so
  • #8 V4LNames::Update
    from /usr/lib/pwlib/device/videoinput/v4l_pwplugin.so
  • #9 PVideoInputDevice_V4L::Open
    from /usr/lib/pwlib/device/videoinput/v4l_pwplugin.so
  • #10 PVideoInputDevice::CreateOpenedDevice
    from /usr/lib/libpt.so.1.10.2
  • #11 PPluginServiceDescriptor::~PPluginServiceDescriptor
  • #12 PThread::PX_ThreadStart
    from /usr/lib/libpt.so.1.10.2
  • #13 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #14 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 1 Snark 2006-10-28 12:13:40 UTC
It looks like it crashed while detecting your video devices... are you sure your driver isn't experimental/buggy ?
Comment 2 André Klapper 2006-10-29 23:38:47 UTC
*** Bug 366992 has been marked as a duplicate of this bug. ***
Comment 3 Damien Sandras 2006-10-30 08:31:21 UTC
It crashes in V4LNames::BuildUserFriendly ().

The code is the following :
PString V4LNames::BuildUserFriendly(PString devname)
{
  PString Result;

  int fd = ::open((const char *)devname, O_RDONLY);
  if(fd < 0) {
    return devname;
  }

  struct video_capability videocap;
  if (::ioctl(fd, VIDIOCGCAP, &videocap) < 0)  {
      ::close(fd);
      return devname;
    }

  ::close(fd);
  PString ufname(videocap.name);

  return ufname;
}


I see nothing there that could trigger a crash except a buggy video driver.


Can one of you provide a backtrace with debug symbols?

Thanks
Comment 4 rpage_is_king 2006-11-01 23:58:34 UTC
The driver (gspcav1-20060925) is relatively new, so it may be buggy. The camera worked in the "Camorama" application, but this was the first time I've attempted to use it with Ekiga. 
Comment 5 Snark 2006-11-05 08:26:28 UTC
I would say : report the bug to the driver authors. We pasted the crashing code here, they should be able to reproduce.
Comment 6 Damien Sandras 2007-01-14 18:56:15 UTC

*** This bug has been marked as a duplicate of 376078 ***