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 443045 - crash in Tasks: Selecting a signature
crash in Tasks: Selecting a signature
Status: RESOLVED DUPLICATE of bug 447797
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-01 21:27 UTC by ncorrare
Modified: 2007-06-15 23:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description ncorrare 2007-06-01 21:27:41 UTC 
What were you doing when the application crashed?
Selecting a signature



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

Memory status: size: 132300800 vsize: 132300800 resident: 40423424 share: 20844544 rss: 40423424 rss_rlim: 4294967295
CPU usage: start_time: 1180733050 rtime: 717 utime: 672 stime: 45 cutime:2 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208727840 (LWP 8776)]
[New Thread -1262908528 (LWP 8870)]
[New Thread -1231012976 (LWP 8796)]
(no debugging symbols found)
0x00e17402 in __kernel_vsyscall ()

+ Trace 137361

Thread 1 (Thread -1208727840 (LWP 8776))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_str_hash
    from /lib/libglib-2.0.so.0
  • #6 g_hash_table_insert
    from /lib/libglib-2.0.so.0
  • #7 em_folder_tree_model_set_folder_info
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #8 em_folder_tree_model_set_folder_info
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #9 em_folder_tree_model_set_folder_info
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #10 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #11 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (32 sec old) ---------------------
(evolution:3005): libebook-CRITICAL **: file e-book.c: line 3807: assertion `source && E_IS_SOURCE (source)' failed
***MEMORY-ERROR***: evolution[3005]: GSlice: assertion failed: sinfo->n_allocated > 0
CalDAV Eplugin starting up ...
** (evolution:8776): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:8776): DEBUG: mailto URL program: evolution
/bin/bash: play: command not found
(evolution:8776): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:8776): 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:8776): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa550000'
(evolution:8776): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa550120'
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-02 01:05:05 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 André Klapper 2007-06-15 23:29:32 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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