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 458637 - crash in Email:
crash in Email:
Status: RESOLVED DUPLICATE of bug 458570
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-20 13:12 UTC by giordanoyoshida
Modified: 2007-07-20 16:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description giordanoyoshida 2007-07-20 13:12:46 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: 129654784 vsize: 129654784 resident: 48885760 share: 31068160 rss: 48885760 rss_rlim: 4294967295
CPU usage: start_time: 1184936892 rtime: 2362 utime: 1857 stime: 505 cutime:135 cstime: 263 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 -1208145168 (LWP 2945)]
[New Thread -1282045040 (LWP 3048)]
[New Thread -1240581232 (LWP 2985)]
[New Thread -1230091376 (LWP 2982)]
(no debugging symbols found)
0x002a7402 in __kernel_vsyscall ()

+ Trace 149340

Thread 4 (Thread -1230091376 (LWP 2982))

  • #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 (231 sec old) ---------------------
localuser:Salvatore being added to access control list
SESSION_MANAGER=local/host208-14-dynamic.60-82-r.retail.telecomitalia.it:/tmp/.ICE-unix/2704
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:2945): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2945): 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:2945): camel-pop3-provider-WARNING **: Bad server response: Arial, Sans; TEXT=
(evolution:2945): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `priv->closed == FALSE' failed
--------------------------------------------------
Comment 1 palfrey 2007-07-20 16:34:54 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 458570 ***