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 482823 - crash in Tasks: configuring email on evo...
crash in Tasks: configuring email on evo...
Status: RESOLVED DUPLICATE of bug 455180
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-03 04:31 UTC by marphil
Modified: 2007-10-07 15:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description marphil 2007-10-03 04:31:34 UTC 
Version: 2.10

What were you doing when the application crashed?
configuring email on evolution


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.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 123392000 vsize: 123392000 resident: 43495424 share: 31703040 rss: 43495424 rss_rlim: 4294967295
CPU usage: start_time: 1191385092 rtime: 405 utime: 372 stime: 33 cutime:1 cstime: 5 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 -1208736032 (LWP 2673)]
[New Thread -1250354288 (LWP 2868)]
[New Thread -1303196784 (LWP 2862)]
[New Thread -1313686640 (LWP 2861)]
[New Thread -1219404912 (LWP 2801)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 167305

Thread 1 (Thread -1208736032 (LWP 2673))

  • #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 /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 g_slist_remove
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (613 sec old) ---------------------
alarm-queue.c:1998 (alarm_queue_add_async) - 0x9141cb0
alarm-queue.c:585 (load_alarms_for_today) - From Wed Oct  3 06:18:** Message: failed to load session from /home/phil/.nautilus/saved-session-W6XNYT
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:2673): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2673): 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:2673): 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:2673): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8f9b018'
(evolution:2673): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8f9b138'
--------------------------------------------------
Comment 1 Suman Manjunath 2007-10-07 15:05:13 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 455180 ***