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 453504 - crash in Tasks: reception imap
crash in Tasks: reception imap
Status: RESOLVED DUPLICATE of bug 444852
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-03 21:40 UTC by ns
Modified: 2007-07-03 23:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description ns 2007-07-03 21:40:13 UTC 
Version: 2.10

What were you doing when the application crashed?
reception imap


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 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 115720192 vsize: 115720192 resident: 46268416 share: 32837632 rss: 46268416 rss_rlim: 4294967295
CPU usage: start_time: 1183498627 rtime: 431 utime: 140 stime: 291 cutime:0 cstime: 17 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 -1208224032 (LWP 2890)]
[New Thread -1314100336 (LWP 2985)]
[New Thread -1230570608 (LWP 2924)]
(no debugging symbols found)
0x00d90402 in __kernel_vsyscall ()

+ Trace 145557

Thread 1 (Thread -1208224032 (LWP 2890))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 g_hash_table_insert
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #8 gdk_pixmap_new
    from /usr/lib/libgdk-x11-2.0.so.0
  • #9 gdk_window_begin_paint_region
    from /usr/lib/libgdk-x11-2.0.so.0
  • #10 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #12 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (43 sec old) ---------------------
** (evolution:2890): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2890): 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:2890): 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:2890): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8e38010'
(evolution:2890): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8e38130'
(evolution:2890): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion `GTK_IS_TREE_MODEL (tree_model)' failed
(evolution:2890): e-data-server-ui-WARNING **: Le fichier de clés n'a pas de groupe « Passwords-Mail »
--------------------------------------------------
Comment 1 Karsten Bräckelmann 2007-07-03 23:20:24 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 444852 ***