Bug 384525 – crash in Ekiga Softphone: Exiting the application ...

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 384525 - crash in Ekiga Softphone: Exiting the application ...


Summary:	crash in Ekiga Softphone: Exiting the application ...


Status:	RESOLVED DUPLICATE of bug 359655

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-12-10 21:38 UTC by felipesouto
Modified:	2006-12-11 16:38 UTC

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

Description felipesouto 2006-12-10 21:38:52 UTC

Version: 2.0.3

What were you doing when the application crashed?
Exiting the application in tray


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

Memory status: size: 104820736 vsize: 0 resident: 104820736 share: 0 rss: 26808320 rss_rlim: 0
CPU usage: start_time: 1165786444 rtime: 0 utime: 320 stime: 0 cutime:286 cstime: 0 timeout: 34 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 -1246992720 (LWP 4613)]
[New Thread -1297613920 (LWP 5406)]
[New Thread -1299186784 (LWP 5360)]
[New Thread -1287300192 (LWP 5088)]
[New Thread -1278907488 (LWP 5086)]
[New Thread -1249068128 (LWP 4953)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 93142

Thread 2 (Thread -1297613920 (LWP 5406))

#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 typeinfo name for PList<OpalConnection>
from /usr/lib/libopal.so.2.2
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 OpalMediaFormatList::~OpalMediaFormatList

Comment 1 Jan Schampera 2006-12-11 05:06:29 UTC

Thanks for the report!

Correct me if I'm wrong guys, but this isn't the common close-on-exit-gnomeVFS bug. This more looks like OPAL or directly/subsequentially PWLib.

Jan

Comment 2 Damien Sandras 2006-12-11 08:30:24 UTC

It must be the same bug. The crash occurs in the thread with gnome_gtk_module_info_get, for which there is no backtrace.

I guess it must be the same bug.

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

Comment 3 Snark 2006-12-11 09:11:54 UTC

Jan, when you see "crash", "exit" and "edgy" in the same bug report, it's a duplicate of bug #359655.

Isn't it possible to write scripts to auto-mark duplicates ?

Comment 4 Jan Schampera 2006-12-11 16:38:21 UTC

I wanted to be sure to not mark a false positive.