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 444410 - crash in Tasks: adding a second exchange...
crash in Tasks: adding a second exchange...
Status: RESOLVED DUPLICATE of bug 432796
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-05 17:14 UTC by jhargus
Modified: 2007-06-06 10:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jhargus 2007-06-05 17:14:05 UTC 
What were you doing when the application crashed?
adding a second exchange account, I really only need the inbox folder from the second account but it would not allow me to subscibe to the folder.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 175882240 vsize: 175882240 resident: 41095168 share: 22282240 rss: 41095168 rss_rlim: 4294967295
CPU usage: start_time: 1181036471 rtime: 745 utime: 708 stime: 37 cutime:1 cstime: 2 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209092384 (LWP 3805)]
[New Thread -1400747120 (LWP 4280)]
[New Thread -1295455344 (LWP 3881)]
[New Thread -1267991664 (LWP 3838)]
[New Thread -1236128880 (LWP 3835)]
(no debugging symbols found)
0x00f89402 in __kernel_vsyscall ()

+ Trace 138496

Thread 5 (Thread -1236128880 (LWP 3835))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/i686/nosegneg/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/nosegneg/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 __nptl_deallocate_tsd
    from /lib/i686/nosegneg/libpthread.so.0
  • #10 start_thread
    from /lib/i686/nosegneg/libpthread.so.0
  • #11 clone
    from /lib/i686/nosegneg/libc.so.6 


----------- .xsession-errors ---------------------
(evolution:3805): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__jhargus@http:__exchange.brentwood.k12.ca.us_exchange__'
(evolution:3805): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3805): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3805): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
(evolution:3805): 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?)
(evolution:3805): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9aadb50'
(evolution:3805): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9aadc70'
warning: .dynamic section for "/usr/lib/libnm_glib.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 palfrey 2007-06-06 10:24:22 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 432796 ***