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 464901 - crash in IP Telephony, VoIP and Video Conferencing: Iniciando o Ekiga. A web...
crash in IP Telephony, VoIP and Video Conferencing: Iniciando o Ekiga. A web...
Status: RESOLVED DUPLICATE of bug 434223
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: High critical
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-09 02:54 UTC by marco.sieben
Modified: 2007-08-09 05:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description marco.sieben 2007-08-09 02:54:49 UTC
Version: 2.0.9

What were you doing when the application crashed?
Iniciando o Ekiga. A webcam Logitech OrbitCam ligou e ficou com o led ligado. o Ekiga não partiu.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: YattaBlues

Memory status: size: 86532096 vsize: 86532096 resident: 33058816 share: 27652096 rss: 33058816 rss_rlim: 4294967295
CPU usage: start_time: 1186627614 rtime: 167 utime: 51 stime: 116 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208781104 (LWP 3284)]
[New Thread -1240466544 (LWP 3396)]
[New Thread -1238611056 (LWP 3394)]
[New Thread -1238344816 (LWP 3393)]
[New Thread -1238013040 (LWP 3390)]
[New Thread -1211597936 (LWP 3345)]
[New Thread -1211331696 (LWP 3343)]
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208781104 (LWP 3284))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 PVideoInputDevice_V4L::Open
    from /usr/lib/pwlib/devices/videoinput/v4l_pwplugin.so
  • #6 PVideoInputDevice::CreateOpenedDevice
    from /usr/lib/libpt_linux_x86_r.so.1.10.7
  • #7 GMVideoGrabber::VGOpen
  • #8 GMVideoGrabber::GMVideoGrabber
  • #9 GMManager::CreateVideoGrabber
  • #10 GMManager::UpdateDevices
  • #11 GMManager::Init
  • #12 GnomeMeeting::Init
  • #13 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (1723 sec old) ---------------------
seahorse nautilus module initialized
Initializing nautilus-image-converter extension
Initializing nautilus-open-terminal extension
Initializing nautilus-flac-converter extension
Initializing nautilus-search-tool extension
seahorse nautilus module initialized
ERROR:dbus.proxies:Introspect error on :1.4:/Updatesd: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did n
Erro ao exibir url: Ocorreu um erro ao iniciar o comando padrão de ação associado a este local.
Erro ao exibir url: Ocorreu um erro ao iniciar o comando padrão de ação associado a este local.
Erro ao exibir url: Ocorreu um erro ao iniciar o comando padrão de ação associado a este local.
Erro ao exibir url: Ocorreu um erro ao iniciar o comando padrão de ação associado a este local.
Erro ao exibir url: Ocorreu um erro ao iniciar o comando padrão de ação associado a este local.
The application 'pup' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
--------------------------------------------------
Comment 1 Snark 2007-08-09 05:50:28 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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