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 458570 - crash in Email:
crash in Email:
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 458637 458639 492014 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-07-20 08:48 UTC by giordanoyoshida
Modified: 2008-05-20 03:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description giordanoyoshida 2007-07-20 08:48:49 UTC
Version: 2.10

What were you doing when the application crashed?



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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 133787648 vsize: 133787648 resident: 53764096 share: 33320960 rss: 53764096 rss_rlim: 4294967295
CPU usage: start_time: 1184920403 rtime: 2365 utime: 1956 stime: 409 cutime:123 cstime: 211 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208878352 (LWP 2880)]
[New Thread -1286112368 (LWP 4637)]
[New Thread -1272288368 (LWP 2926)]
[New Thread -1230824560 (LWP 2919)]
(no debugging symbols found)
0x003f4402 in __kernel_vsyscall ()

Thread 2 (Thread -1286112368 (LWP 4637))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 camel_pop3_engine_command_new
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
  • #7 camel_pop3_store_expunge
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
  • #8 camel_pop3_delete_old
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
  • #9 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so
  • #10 camel_folder_sync
    from /usr/lib/libcamel-provider-1.2.so.10
  • #11 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6


----------- .xsession-errors (125 sec old) ---------------------
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:2880): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2880): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:2880): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `priv->closed == FALSE' failed
(evolution:2880): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:2880): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa5cf010'
(evolution:2880): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa5cf130'
--------------------------------------------------
Comment 1 palfrey 2007-07-20 16:34:05 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 and
reopen this bug or report a new one. Thanks in advance!
Comment 2 palfrey 2007-07-20 16:34:54 UTC
*** Bug 458637 has been marked as a duplicate of this bug. ***
Comment 3 palfrey 2007-07-20 16:34:55 UTC
*** Bug 458639 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2007-12-19 03:40:56 UTC
*** Bug 492014 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2007-12-19 03:41:17 UTC
Thanks for taking the time to report this bug.
Unfortunately, the 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 help fixing this by installing some debugging packages [1], start the application as normal, and try to 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] Please install debug 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 6 Akhil Laddha 2008-05-20 03:49:14 UTC
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.22.x or later), please reopen. thanks in advance.