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 443415 - crash in Tasks: Trying to select
crash in Tasks: Trying to select
Status: RESOLVED DUPLICATE of bug 433568
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-03 02:56 UTC by pem
Modified: 2007-07-01 00:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description pem 2007-06-03 02:56:45 UTC
What were you doing when the application crashed?
Trying to select "Sent" folder on "On This Computer".


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 700370944 vsize: 700370944 resident: 52350976 share: 22409216 rss: 52350976 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180835763 rtime: 2867 utime: 2633 stime: 234 cutime:2 cstime: 3 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 46912496410208 (LWP 2594)]
[New Thread 1084229968 (LWP 3007)]
[New Thread 1105475920 (LWP 2655)]
[New Thread 1094719824 (LWP 2619)]
(no debugging symbols found)
0x0000003b3f20d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496410208 (LWP 2594))

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


----------- .xsession-errors (150 sec old) ---------------------
(evolution:2594): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error
(evolution:2594): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `buf != NULL' failed
(evolution:2594): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error
(evolution:2594): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `buf != NULL' failed
(evolution:2594): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error
(evolution:2594): 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?)
(evolution:2594): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x863000'
(evolution:2594): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x862c00'
--------------------------------------------------
Comment 1 palfrey 2007-06-03 10:57:45 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 Karsten Bräckelmann 2007-07-01 00:22:05 UTC
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 433568 ***