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 391669 - crash in Ekiga Softphone: Trying to call a number ...
crash in Ekiga Softphone: Trying to call a number ...
Status: RESOLVED DUPLICATE of bug 367982
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: High critical
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-01 22:09 UTC by alexander
Modified: 2007-01-14 19:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description alexander 2007-01-01 22:09:11 UTC
Version: 2.0.3

What were you doing when the application crashed?
Trying to call a number using sipgate.de


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.17.2 2006-11-14 (Ubuntu)
BugBuddy Version: 2.17.3

System: Linux 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 124338176 vsize: 0 resident: 124338176 share: 0 rss: 30818304 rss_rlim: 0
CPU usage: start_time: 1167688966 rtime: 0 utime: 3678 stime: 0 cutime:1559 cstime: 0 timeout: 2119 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 -1247459632 (LWP 32332)]
[New Thread -1279607920 (LWP 32515)]
[New Thread -1360589936 (LWP 32496)]
[New Thread -1279075440 (LWP 32495)]
[New Thread -1278809200 (LWP 32425)]
[New Thread -1278542960 (LWP 32424)]
[New Thread -1278276720 (LWP 32392)]
[New Thread -1278010480 (LWP 32391)]
[New Thread -1277281392 (LWP 32376)]
[New Thread -1277015152 (LWP 32375)]
[New Thread -1276748912 (LWP 32374)]
[New Thread -1276482672 (LWP 32373)]
[New Thread -1276216432 (LWP 32372)]
[New Thread -1275933808 (LWP 32371)]
[New Thread -1360323696 (LWP 32357)]
[New Thread -1360057456 (LWP 32356)]
[New Thread -1359762544 (LWP 32352)]
[New Thread -1351369840 (LWP 32346)]
[New Thread -1249707120 (LWP 32335)]
[New Thread -1249440880 (LWP 32334)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 3 (Thread -1360589936 (LWP 32496))

  • #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 ??
  • #5 PString::Compare
    from /usr/lib/libpt.so.1.10.2
  • #6 PHashTable::Table::GetElementAt
    from /usr/lib/libpt.so.1.10.2
  • #7 PAbstractDictionary::AbstractSetAt
    from /usr/lib/libpt.so.1.10.2
  • #8 SIPTransaction::Start
    from /usr/lib/libopal.so.2.2
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 PString::~PString
  • #13 SIPConnection::OnReceivedAuthenticationRequired
    from /usr/lib/libopal.so.2.2
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??


----------- .xsession-errors (392 sec old) ---------------------
(nautilus:22235): Gtk-CRITICAL **: gtk_tree_model_sort_get_value: assertion `VALID_ITER (iter, tree_model_sort)' failed
(nautilus:22235): GLib-GObject-CRITICAL **: g_object_set_property: assertion `G_IS_VALUE (value)' failed
(nautilus:22235): GLib-GObject-CRITICAL **: g_value_unset: assertion `G_IS_VALUE (value)' failed
(nautilus:22235): Gtk-CRITICAL **: gtk_tree_model_sort_iter_next: assertion `tree_model_sort->stamp == iter->stamp' failed
(nautilus:22235): Gtk-CRITICAL **: file gtktreeview.c: line 6054 (do_validate_rows): assertion `gtk_tree_model_iter_next (tree_view->priv->model, &iter)' failed.
There is a disparity between the internal view of the GtkTreeView,
and the GtkTreeModel.  This generally means that the model has changed
without letting the view know.  Any display from now on is likely to
be incorrect.
Fenstermanager-Warnung: Ungültiges WM_TRANSIENT_FOR-Fenster 0x2400043 festgelegt für 0x24002c5 ().
--------------------------------------------------
Comment 1 Damien Sandras 2007-01-02 18:46:17 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Damien Sandras 2007-01-14 19:11:53 UTC

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