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 450301 - crash in Email: scaricando posta
crash in Email: scaricando posta
Status: RESOLVED DUPLICATE of bug 426227
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 454593 456193 457866 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-23 09:44 UTC by jurangel
Modified: 2007-09-20 17:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jurangel 2007-06-23 09:44:06 UTC
Version: 2.10

What were you doing when the application crashed?
scaricando posta


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 628240384 vsize: 628240384 resident: 54525952 share: 33366016 rss: 54525952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182591182 rtime: 604 utime: 556 stime: 48 cutime:2 cstime: 7 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 46912496377440 (LWP 4450)]
[New Thread 1126189392 (LWP 4631)]
[New Thread 1115699536 (LWP 4617)]
[New Thread 1189128528 (LWP 4494)]
(no debugging symbols found)
0x000000377ee0d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496377440 (LWP 4450))

  • #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 gtk_widget_unparent
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #28 ??
    from /lib64/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #31 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #33 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #34 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #35 ??
    from /lib64/libgobject-2.0.so.0
  • #36 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #37 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #38 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #39 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #40 ??
    from /usr/lib64/libedataserverui-1.2.so.8
  • #41 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #42 ??
    from /lib64/libglib-2.0.so.0
  • #43 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #44 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #45 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (26 sec old) ---------------------
(evolution:4450): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x894b70'
(evolution:4450): e-data-server-ui-WARNING **: Il file chiavi non presenta la chiave "pop:__alessio.fialdinini@pop.tiscali.it_"
(evolution:4450): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Impossibile connettersi al server POP pop.tiscali.it.
Errore nell'invio della password: Operation now in progress
(evolution:4450): 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:4450): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x894f70'
(evolution:4450): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x894770'
(evolution:4450): e-data-server-ui-WARNING **: Il file chiavi non presenta la chiave "pop:__alessio.fialdini@pop.tiscali.it_"
--------------------------------------------------
Comment 1 palfrey 2007-07-07 21:27:41 UTC
*** Bug 454593 has been marked as a duplicate of this bug. ***
Comment 2 palfrey 2007-07-12 11:20:54 UTC
*** Bug 456193 has been marked as a duplicate of this bug. ***
Comment 3 palfrey 2007-08-17 13:07:51 UTC
*** Bug 457866 has been marked as a duplicate of this bug. ***
Comment 4 palfrey 2007-09-20 17:33:45 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 ***