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 102230 - Carsh video logitech cam + pwc
Carsh video logitech cam + pwc
Status: RESOLVED DUPLICATE of bug 98179
Product: ekiga
Classification: Applications
Component: Documentation
unspecified
Other other
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2003-12-30 18:24 UTC by misi
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description misi 2002-12-30 18:23:51 UTC 
Package: gnomemeeting
Severity: major
Version: 0.94.1
Synopsis: Carsh video logitech cam + pwc
Bugzilla-Product: gnomemeeting
Bugzilla-Component: Documentation
BugBuddy-GnomeVersion: 2.0 (2.0.6)

Description:
Description of Problem:
Crash after a few minutes!

Steps to reproduce the problem:
1. video stop workinkg on the other side
2. wait a few minutes
3. 

Actual Results:
crash

Expected Results:
work :)

How often does this happen?

every timre
Additional Information:




Debugging Information:

Backtrace was generated from '/usr/local/bin/gnomemeeting'

0x41809a39 in ?? ()

+ Trace 32155

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 GMH323Gatekeeper::Main
    at gatekeeper.cpp line 206
  • #19 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-12-30 13:23 -------

Reassigning to the default owner of the component, gnomemeeting-maint@bugzilla.gnome.org.
Comment 1 Damien Sandras 2002-12-30 18:41:06 UTC 
Most probably a dup of 98179 but your backtrace is not valid.
If you are using Redhat 8 or Debian, we can provide you binaries of CVS so that you can test it is fixed. Please reopen in that case.

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