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 500795 - crash in Tasks: TLS connection to a pop3...
crash in Tasks: TLS connection to a pop3...
Status: RESOLVED DUPLICATE of bug 426227
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-01 03:57 UTC by outtaluck
Modified: 2007-12-04 17:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description outtaluck 2007-12-01 03:57:44 UTC
Version: 2.10

What were you doing when the application crashed?
TLS connection to a pop3 server, cert is misconfigured, came up bad, then Evolution crashed


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

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 777785344 vsize: 777785344 resident: 166817792 share: 44748800 rss: 166817792 rss_rlim: 18446744073709551615
CPU usage: start_time: 1196087000 rtime: 19710 utime: 16600 stime: 3110 cutime:45 cstime: 132 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496416112 (LWP 1540)]
[New Thread 1168148816 (LWP 30961)]
[New Thread 1136679248 (LWP 30944)]
[New Thread 1084229968 (LWP 2405)]
[New Thread 1220864336 (LWP 1561)]
(no debugging symbols found)
0x00000038d240d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496416112 (LWP 1540))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free1
    from /lib64/libglib-2.0.so.0
  • #7 g_slist_foreach
    from /lib64/libglib-2.0.so.0
  • #8 pango_layout_line_unref
    from /usr/lib64/libpango-1.0.so.0
  • #9 ??
    from /usr/lib64/libpango-1.0.so.0
  • #10 ??
    from /usr/lib64/libpango-1.0.so.0
  • #11 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #14 ??
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 gtk_widget_unparent
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #28 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #29 ??
    from /lib64/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #31 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #32 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #33 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #35 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #36 ??
    from /lib64/libgobject-2.0.so.0
  • #37 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #38 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #39 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #40 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #41 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #42 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #43 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #44 ??
    from /lib64/libglib-2.0.so.0
  • #45 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #46 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #47 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
 CConn:       Throughput 20123 kbit/s - changing to full colour
 CConn:       Using pixel format depth 24 (32bpp) little-endian rgb888
 CConn:       Using hextile encoding
(evolution:1540): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:1540): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x883450'
(evolution:1540): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x883050'
warning: .dynamic section for "/usr/lib64/librsvg-2.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib64/libgsf-1.so.114" is not at the expected address (wrong library or version mismatch?)
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff2adfd000
--------------------------------------------------
Comment 1 Susana 2007-12-02 12:57:30 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.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk,
glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are
provided by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces

Comment 2 Tobias Mueller 2007-12-04 17:15:42 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 426227 ***