Bug 369992 – crash in Ekiga Softphone: j'était juste sur intern...

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 369992 - crash in Ekiga Softphone: j'était juste sur intern...


Summary:	crash in Ekiga Softphone: j'était juste sur intern...


Status:	RESOLVED DUPLICATE of bug 364113

Product:	ekiga
Classification:	Applications
Component:	general
Version:	2.0.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Ekiga maintainers
QA Contact:	Ekiga maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-03 13:36 UTC by buko_92
Modified:	2006-11-03 21:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description buko_92 2006-11-03 13:36:33 UTC

Version: 2.0.3

What were you doing when the application crashed?
j'était juste sur internet !!?


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

Memory status: size: 97759232 vsize: 0 resident: 97759232 share: 0 rss: 26034176 rss_rlim: 0
CPU usage: start_time: 1162564245 rtime: 0 utime: 116 stime: 0 cutime:104 cstime: 0 timeout: 12 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 -1246980432 (LWP 17202)]
[New Thread -1291068512 (LWP 17224)]
[New Thread -1290802272 (LWP 17223)]
[New Thread -1280861280 (LWP 17221)]
[New Thread -1282409568 (LWP 17219)]
[New Thread -1249236064 (LWP 17212)]
[New Thread -1248969824 (LWP 17211)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 82341

Thread 1 (Thread -1246980432 (LWP 17202))

#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 g_string_new
from /usr/lib/libglib-2.0.so.0
#5 gnome_vfs_uri_to_string
from /usr/lib/libgnomevfs-2.so.0
#6 fs_module_create
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#7 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#8 ??
#9 ??
#10 ??
#11 ??
from /usr/lib/libgthread-2.0.so.0
#12 ??
#13 ??
from /usr/lib/libglib-2.0.so.0
#14 ??
#15 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#16 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 PList<PString>::~PList
#22 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#23 ??
#0 __kernel_vsyscall

Comment 1 Damien Sandras 2006-11-03 16:38:15 UTC


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

Comment 2 Karsten Bräckelmann 2006-11-03 21:56:38 UTC

Nope, different issue...

Comment 3 Karsten Bräckelmann 2006-11-03 21:57:21 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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