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 445651 - crash in Tasks: I was just closing out o...
crash in Tasks: I was just closing out o...
Status: RESOLVED DUPLICATE of bug 334966
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-09 01:34 UTC by jprigot
Modified: 2007-06-12 00:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jprigot 2007-06-09 01:34:22 UTC 
What were you doing when the application crashed?
I was just closing out of Evolution.


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.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 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: 618463232 vsize: 618463232 resident: 39661568 share: 21950464 rss: 39661568 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181352565 rtime: 683 utime: 638 stime: 45 cutime:65 cstime: 18 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 46912501158048 (LWP 4439)]
[New Thread 1178904912 (LWP 4534)]
[New Thread 1126455632 (LWP 4464)]
(no debugging symbols found)
0x0000003a7340d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 139483

Thread 1 (Thread 46912501158048 (LWP 4439))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib64/libc.so.6
  • #4 e_shell_window_set_title
  • #5 ??
  • #6 GNOME_Evolution_ShellView_setTitle
    from /usr/lib64/evolution/2.10/libeshell.so.0
  • #7 e_component_view_set_title
    from /usr/lib64/evolution/2.10/libeshell.so.0
  • #8 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /lib64/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #11 ??
    from /lib64/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #13 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #14 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (154 sec old) ---------------------
(evolution:4439): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:4439): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4439): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4439): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:4439): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4439): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:4439): 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?)
BBDB spinning up...
(evolution:4439): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x852cc0'
(evolution:4439): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x852ac0'
--------------------------------------------------
Comment 1 André Klapper 2007-06-12 00:46:34 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 334966 ***