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 504209 - crash in Tasks: I was trying to connect ...
crash in Tasks: I was trying to connect ...
Status: RESOLVED DUPLICATE of bug 426807
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-18 09:51 UTC by okko
Modified: 2008-03-20 13:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description okko 2007-12-18 09:51:25 UTC
Version: 2.10

What were you doing when the application crashed?
I was trying to connect to a new EMail account on IMAP-server,
which sent back error messages.
And Evolution keeps asking password totally disregarding Cancel-button
making it impossible todo anything usefull....


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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 782057472 vsize: 782057472 resident: 96956416 share: 45232128 rss: 96956416 rss_rlim: 18446744073709551615
CPU usage: start_time: 1196935775 rtime: 16227 utime: 14477 stime: 1750 cutime:36267 cstime: 3880 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 46912496451728 (LWP 15597)]
[New Thread 1084229968 (LWP 21999)]
[New Thread 1136679248 (LWP 21993)]
[New Thread 1157925200 (LWP 21991)]
[New Thread 1126189392 (LWP 15761)]
[New Thread 1147435344 (LWP 15630)]
[New Thread 1094719824 (LWP 15602)]
(no debugging symbols found)
0x000000306c20d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496451728 (LWP 15597))

  • #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_free_chain_with_offset
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #8 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #11 g_datalist_clear
    from /lib64/libglib-2.0.so.0
  • #12 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #16 ??
    from /lib64/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #19 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 g_object_run_dispose
    from /lib64/libgobject-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 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #24 ??
    from /lib64/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #27 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #28 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #29 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #32 ??
    from /lib64/libgobject-2.0.so.0
  • #33 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #34 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #35 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #36 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #37 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #38 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #39 ??
    from /lib64/libgobject-2.0.so.0
  • #40 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #41 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #42 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #43 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #44 ??
    from /usr/lib64/libedataserverui-1.2.so.8
  • #45 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #46 ??
    from /lib64/libglib-2.0.so.0
  • #47 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #48 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #49 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (25 sec old) ---------------------
(evolution:15597): e-data-server-ui-WARNING **: Key file does not have key 'imap:__jokkonen.paymox@imap.otaverkko.fi_'
(evolution:15597): e-data-server-ui-WARNING **: Key file does not have key 'imap:__jokkonen.paymox@imap.otaverkko.fi_'
(evolution:15597): e-data-server-ui-WARNING **: Key file does not have key 'imap:__jokkonen.paymox@imap.otaverkko.fi_'
(evolution:15597): e-data-server-ui-WARNING **: Key file does not have key 'imap:__jokkonen.paymox@imap.otaverkko.fi_'
(evolution:15597): e-data-server-ui-WARNING **: Key file does not have key 'imap:__jokkonen.paymox@imap.otaverkko.fi_'
(evolution:15597): e-data-server-ui-WARNING **: Key file does not have key 'imap:__jokkonen.paymox@imap.otaverkko.fi_'
(evolution:15597): e-data-server-ui-WARNING **: Key file does not have key 'imap:__jokkonen.paymox@imap.otaverkko.fi_'
(evolution:15597): e-data-server-ui-WARNING **: Key file does not have key 'imap:__jokkonen.paymox@imap.otaverkko.fi_'
--------------------------------------------------
Comment 1 Tobias Mueller 2008-03-20 13:35:37 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 426807 ***