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 484749 - crash in Tasks: trying to change the SMT...
crash in Tasks: trying to change the SMT...
Status: RESOLVED DUPLICATE of bug 407187
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-08 14:46 UTC by mlshaw
Modified: 2007-10-16 05:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mlshaw 2007-10-08 14:46:41 UTC
Version: 2.10

What were you doing when the application crashed?
trying to change the SMTP settings


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 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 763633664 vsize: 763633664 resident: 73072640 share: 41799680 rss: 73072640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191851008 rtime: 985 utime: 886 stime: 99 cutime:21 cstime: 16 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 46912498528416 (LWP 3249)]
[New Thread 1105209680 (LWP 4376)]
[New Thread 1115965776 (LWP 3385)]
[New Thread 1084229968 (LWP 3331)]
(no debugging symbols found)
0x00000038b6e0d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912498528416 (LWP 3249))

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


----------- .xsession-errors (39 sec old) ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
(evolution:3249): e-data-server-DEBUG: Loading categories from "/home/mlshaw/.evolution/categories.xml"
(evolution:3249): e-data-server-DEBUG: Loaded 29 categories
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
(evolution:3249): 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:3249): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8545a0'
(evolution:3249): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8549a0'
--------------------------------------------------
Comment 1 Akhil Laddha 2007-10-16 05:05:45 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 407187 ***